Is it bad now I seem to take some pleasure whenever I see someone/something on my team blow up and go "¯\_(ツ)_/¯ not my code, not my problem"

2 problems with that
1) people leave, take holiday, etc, at some point it WILL be your problem
2) you aren't that good a programmer. Nobody is.

Yeah but leaving shit code around will blow up in your face eventually. You should always try to clean any mess even when it's not yours.
If you don't, is like laughing because the other cabin on the titanic is filling up with water.

In my old job no one would listen to my concerns about quality. The devs did a shit job, management didn't care how it got done as long as it worked today, there was no architecture to speak of and the code written by most of the team was genuinely the worst it could be whilst still working. Like 2000 line copy paste functions, dumping 10 million r cords in memory to do an in memory join and then garbage collect all but 5 records.

In that environment I also started to take pleasure in the ship sinking.

@fjrevoredo

> laughing because the other cabin on the titanic is filling up with water

Hahahaha, the loser next door is gonna be all soaked!

@fjrevoredo well but exactly someone else's ap been causing prod issues bc soaking the db. I have no idea what it is and don't want to.