Secondly, you can't know he hasn't worked on mature systems (he didn't say). Most people learn by working with a variety of systems that are at different stages (greenfield to twilight), and more importantly with different quality (poor versus good architecture/systems/teams).
A long period working on one good system may help a few people learn, but from what I have seen, it often doesn't (I have worked with crap programmers on mature systems).
Hopefully GP answers for themselves.
https://www.joelonsoftware.com/2001/07/21/good-software-take...
Sure a CRUD MVP can be cranked out in six months or less, but that's not what we're talking about.
Photoshop is an example of a product that still maintains its market fit after decades, and why folks complain about alternatives.
The part I disagree with is the idea that you get to done. Photoshop is a great example. It's over 30 years old. Would Photoshop still hold its market position if it reached maturity 20 years ago and said "we're done?" Ignore UI changes and support for new OSes for a second. Would Photoshop be the market leader without Camera RAW support? High Dynamic Range? GPU acceleration?
Just look at Photoshop's version history:
http://en.wikipedia.org/wiki/Adobe_Photoshop_version_history
You don't have to agree with every change they've made, but there's a lot of serious features that got released after Year 10 that are need-to-have features. I don't think Photoshop 5.5 was the last Photoshop professionals needed.
Meanwhile, Affinity Photo is only four years old, and while if you had to choose between them Photoshop still has a lot of things Affinity doesn't, I'd pick it over Photoshop 5.5 in a heartbeat.
> So, it takes a long time to write a good program, but when it’s done, it’s done. Oh sure, you can crank out a new version every year or two, trying to get the upgrade revenues, but eventually people will ask: “why fix what ain’t broken?”
Just because you've been working on shit show projects that doesn't mean all projects are mismanaged like that.
Billions of in-house apps, for companies > ten years old.
The link above details several more, read it.
P.S. Gnaritas, you're dead. Tried vouching, didn't work.
Plenty of companies aren't attracted to the new shiny.
So you've never worked in good code, that's all. Most of the world runs on software evolved over greater than 10 years. Everything you said is wrong, because you've been surfing trendy crap that businesses mostly ignore. Good architects don't use immature languages that might not be around in 10 years, they're smarter than that.
Btw. The supplier was one of the leading and most hip e-commerce (consulting) companies in my country.
I've seen and been in involved with others too by all kinds of companies. They are everywhere.
People changing jobs/teams faster than that may simply never experience a feedback cycle on the real, long-term quality of their work.
That is quite different than the CRUD web application that most people are working with.
This is what differentiates as a startup from a real company.