3 ms·
> towards unecessarily complicated development processes and architectures please note that what's "unnecessary" for you is not necessarily unnecessary for ot
by je42 6y ago
> towards unecessarily complicated development processes and architectures
please note that what's "unnecessary" for you is not necessarily unnecessary for others.
this is an important point.
i guess what these projects need is a way to communicate explicitly the costs of maintenance and developer mind-share when adding more complex features to their product.
Because especially as small dev team it is difficult to figure out these costs during a short evaluation of the software, is not easy to pick the best tool for the job unless some members have got experience in some previous job with these tools.
- tanseydavid 6y agoI think your point is slightly off in its 'angle'. Consider that "unnecessarily-complicated" and "unnecessary" do NOT mean the same thing -- particularly in this case.
- je42 6y agothat depends on the interpretation. most people don't mean there is a simpler implementation that has the same feature set and execution properties. Most people mean it has features i don't need, hence it is too complicated