[majesticglue]

> Does the author hold some resentment for senior engineers or something?

Sounds like it.

I worked at a company where some of my team leads were business persons (and had no coding experience) who just happened to start working on backend (before i started working there) and setup a codebase. It probably was beneficial at the time because they knew what to build and what type of value it could bring...

But of course, when the team started expanding, people realized the database had one of the absolute awful data modeling that was completely unworkable. No one can work on it because of all the complicated SQL queries (we are talking full page SQL queries) required to make any kind of changes.

They wanted a new version of the app, but no one wanted to touch that mess but they were literally stuck because they had valuable data formatted in this conglomerate mess. For example, the app would take like 5 seconds to load, and make 5-10 different api calls for what should be single api calls to the backend. Fortunately it was an internal app so performance wasn't as big an issue, but many people were using it. So there were so many bugs and requests of this app but no one can address them whatsoever, not even the person who built the app. And yes, it was THAT bad.

They wanted us to rebuild that same app, but not rework the backend because of how long it might take, and even 1-2 years later, the app looked better but...the bugs to address are still nearly impossible without a reworked backend. They may have gotten users...but I'm pretty sure they wasted more money on trying to maintain the thing than how much it benefitted the company.

Gotta love business people loving the "anyone can do it!". And code maintenance in the backburner like usual. As long as the app attracts "users", that's all that matters right?