3 ms·

This. This is the argument I'm exhausted having. Rushing development works for... maybe a week. After that, every time, it takes longer overall than if it'd bee

This. This is the argument I'm exhausted having. Rushing development works for... maybe a week. After that, every time, it takes longer overall than if it'd been done "right" the first time. Like a desk, you get one layer of crap and clutter. More than that and everything begins to teeter and fall. That said - you definitely have to ask yourself (as a developer) or your engineers (as management) "is there a simpler way?". But "simpler" is not the same as "rushed", even if both are "faster" - it's just a question of "on what timeline". Faster today? This week? This month? This quarter? This year?

Towaway69 3y ago
What's the old saying - nine pregnant people won't produce a child in one month. I think that comes from the Mythical Man Month but not sure. I think "faster" has been replaced by "profit". Is there a more profitable way of doing it. Etc. Hence things such as AI/CoPilot and the rest. We as developers have lost the craftsmanship that coding once was. Crafting a good bit of code that might just be a single line but which has elegance and conciseness to get the job done just right.