Based on your experience and knowledge, can you wager a guess on the percentage of dev/production codebases at companies are actual, beautifully written, architecturally sound constructions and not a nightmare of a (spaghetti) mess that keeps requiring new architects/ai engineers/senior devs/whatever to maintain (or rewrite)? In my personal experience... let's see.. about 20% or less of all the companies I worked at. That's sad. lol

I think the only places that can afford it are places like IBM or where the business is reliability over "features"

@BordedDev The beautifully designed one was a startup... GASP. :O lol

Easy. Look at the curve of IT engineer salaries. That pretty much reflects the distribution of quality code.

Good engineers aren't paid for trade secrets. They'll mostly push for divulgation, because that leaves their mark (and possible portfolio), and have the luxury to push, argue and/or ignore.

So they'll always be in demand, but they are expensive, and thus, companies pressure their mid devs (because they don't wanna pay a senior) to take responsibility without compensation.

Quality will be just around 90v phase degrees behind.

The knowledgeable senior did his job and left. Juniors need to pick the slack and become seniors. That's the phase disparity, and in the middle, spaghetti happens.

0%.
No database is ever that well written. They are all "not that bad" at best.

@BordedDev It's not about being able to afford it.

Most of the financial industry runs on VBA macros and desperate interns who don't mind coming in at 5am to "run the spreadsheets".

Not exactly spaghetti code, but still spaghetti architecture...

We have systems that get and send data from one system to an other. The amount of new systems added increases.

So now, people are creating more and more custom connectors from 1 system to an other.

I am really considering to move everything to a data backbone and just have very small microservices for each app to get data the software needs from the bus or put data events on the bus. But where to start...

I'm kinda building some spaghetti at my own horror due to having no fucking time to architect something properly. Deadlines set before I started, people didn't properly understand the scope, scope creep happening... And the pressure is on me to perform. This industry disgusts me, but it pays me well enough to be able to afford a decent comfortable existence.

Thankfully the backend is Laravel, so that's easy enough to kind of avoid spaghetti

@Grumm I had to work with a spaghetti architecture before. It was the hardest to debug I ever encountered. lmao

@donkulator if they need desperate interns they can't afford it

I was at a startup for three years and we had one large monolithic codebase. It was honestly pretty good .. at least the domains I worked on. Some of it wasn't great just because it was in Ruby (types, or even Python-style type hinting are a wonderful thing).

But because everyone was working on the same code base, any refactoring ideas tended to happen in bulk. Redoing structure and packaging was discussed with everyone and we'd see huge changes implemented very quickly. There were a LOT of test .. so many it took ~15 minutes to run them split over 15 nodes! (one guy tried to run them on his laptop and it took 8 hours overnight).

Anything merged in would get deployed to production .. so continual release 8~10 times a day or more.

There were some not great things, but overall it was pretty damn impressive. I got laid off from there, along with 1/3 of engineering, back in March. Doubt they'll get 2 more years as a company.

@djsumdog Nice to see some nice CI/CD. I'm surprised they were so organized. I do remember working at a company where tests took 15 minutes as well. I found it an annoyance. lol. Sorry to hear about the lay-off. It sounds like they made some strange decisions.