[atmosx]

There was a similar thread few weeks ago, my take was along these lines:

In this day and age the only way for most companies to beat the market is to deliver fast, what engineers perceive as quality doesn't make sense from a business perspective.

If you want to work on high quality software you can either work in open source projects which have high quality code or avoid highly paying startups and move to an industry that cannot afford low quality software. These industries are usually boring, in the sense that they use old programming languages and frameworks that "just work". They have policies and amounts of bureaucracy/paperwork to go along with it and ensure quality, security and compliance at all levels.

There might be a sweet spot between the extremes, but I never came across one to be honest. My experience is mostly with the first group, which I must say that for all the whining "about quality" and "developers <...>" I most definitely enjoy and to a large extend accept the flaws because I understand the reasoning that goes with it. I'm putting a fight ofc as you do, when I believe quality must improve, but that's about it.

[throw4238]

Yeah I think poor use of logic is most of the problem. No one's 100% logical... but you get pulled into these discussions asking just how quickly you can get this out... and it just repeats. At the start of the project they'll talk tech debt/spikes/whatever... but as you keep going it's just churn and burn and you really have to do extra/free work if you want to inject more quality.

There's definitely a spectrum from trash to gold plating... but most web shops are in 0 danger of wasting time or gold plating.

I understand the need to go faster from a business perspective... what I don't understand is the lying. Why not just tell us what the plan is so we can plan accordingly?