I have another post BTW:
“Dishonesty of Optimizing for Developer Time”
Picture this: a clash of ideals, a tug-of-war between two schools of thought, each passionately championing their cause. On one side, we have those who chant the mantra of developer time and productivity, swearing by the motto, “Code fast, iterate faster!” On the other side stand the valiant defenders of performance, robustness, and correctness…
https://prma.dev/dishonesty-of-optimizing-for-developer-time/
@Amirography theres a lot to this really.
But anyone arguing against using good tooling is usually just saying: we dont want to pay (time, money) for quality.
And when i say quality, its not like getting mayonaise in your sandwhich, its getting bread that doesn't have flakes of granite from the mill, and rat droppings in it.
@Amirography and when I say they dont want to invest it is in writing tests, and learning better tools.
I used to be in a place that used a 15 year old web framework, simply because they did not wish to spend the dough to let their devs catch up with the industry. In all honesty they had horrible practices in place due to decisions from management.