This is why I usually pitch formal specification as "you build your program faster and spend less time debugging it later." Framing it as a cost-saving measure over a "well ya GOTTA be correct" measure.
I agree that that is the pragmatic approach given market constraints, but the market is not providing greater value in driving this hack-and-patch approach.
Re:Think in Math, Write in Code
by 1PlayerOne on Friday July 19, 2019 @02:08PM
(#20481044)
So true. Slick presentation, indifferent or bad design and implementation. And then patching and billing client all the long day. Sad!
Rarely do companies and startups have the luxury to just lean back and take their time. It's a race against competitors, and everyone wants the advantage of being first.
I don't blame the devs, as much as I blame the market. People start taking shortcuts when they're judged by how fast they can crank out codes, and whether they can finish their sprints on time. You develop a culture of constantly putting out fires.
Hell, for some consulting firms this is a profitable business model: Deliver a partially working product, then spend 10-15 years on patching it up, on your clients bill.