News for hackers. Stuff that matters.
Re:Ask HN: Is it better to be quick generalist or a slow spe... by merek on Thursday August 25, 2022 @06:55AM (#32592036)
Any decent manager who demands immediate delivery better be aware of the long term costs. In the long run, it's usually cheaper to deliver a well-built feature over a longer time period, compared to a poorly built feature delivered promptly.

https://martinfowler.com/articles/is-quality-worth-cost.html

Re:Ask HN: Is it better to be quick generalist or a slow spe... by gnz11 on Thursday August 25, 2022 @08:10AM (#32592617)
For this to be effective, it has to be understood all the way to the top. The problem I see is that managers are often not technical enough and simply want to appease their bosses with something tangible ... or they are technical, understand this but their boss is not technical, in which case they end up doubling down anyway to appease their boss. Odds are your middle manager has very little clout to argue for much anyway.
Re:Ask HN: Is it better to be quick generalist or a slow spe... by sph on Thursday August 25, 2022 @08:26AM (#32592779)
> In the long run, it's usually cheaper to deliver a well-built feature over a longer time period, compared to a poorly built feature delivered promptly.

It is better in theory, but not in practice.

A startup needs to deliver ASAP, and doesn't care if something is built carefully if a competitor beats you out the door with a subpar product. And that applies to any size company in fact.

If you want to take your time doing it well, work for yourself. Because out there what matters the most is delivering as quickly as possible.

Re:Ask HN: Is it better to be quick generalist or a slow spe... by dev_0 on Thursday August 25, 2022 @08:19PM (#32601778)
Oh the ThoughtWorks gang... it's about billing the customers by dragging the project longer for quality and therefore earning more