Is leadership's willingness to accept shoddy code and a shoddy deployment process, as long as you can develop shoddy features early, a common theme among startups?

I really get a "not my problem when I sell this business" vibe from this attitude.

Is it only startups though? I feel like that's everywhere. Leaderships only care about money. Some have slightly more longer term vision than others.

Software craftsmanship and professional development I feel are always fighting with each other since you can usually on my optimize two out of the three things: Cost, dev speed, quality

Almost all start ups are looking to sell out in one form or another. Since code quality isn't in the business portfolio, businesses don't care until it's a problem

Trick is to _make_ it a problem 😜.

Productivity metrics, frequent presentations of problems + potentially solutions, and education pieces from seniors helped us

There's this thing... Every company has it.

At best once every few years, at worst every few days.

I call it the "Itoldyousobutyoudidntlisten".

When suddenly hardware isn't enough to scale out all the fuckety...

When people get fed up and suddenly there's no more team, but lone survivor and noone has a clue...

Etc.

That's when things completely stop working and there is really no profit anymore.

If you encounter a "Itoldyousobutyoudidntlisten"...

Go to your doctor. Get a leave of absent for two weeks. Barricade yourself in after a supermarket spree. Disable all communication devices.

After 2 weeks carefully turn on the communication devices, best without vibration mode (or if you feeling frisky.... You know where to stick it. :)).

And just grab some of the left over nachos and read up on all the fun mayhem you missed and you definitely not want to deal with.

Get a new job.... Probably take a shower first and do some grooming, 2 weeks of isolation might leave you in a non representative state.

@IntrusionCM lmao, this comment reads like a whole rant in and it of itself