"Biggest challenge you overcame as a dev?"
Overcame? I wish! I'm in the midde of fixing the worst legacy code clusterfuck I have ever seen...
Yes, it's even wayyyy worse than WorstPress...

There are days where my coworkers hear profuse laughter coming out of my lone bureau, some of them might already be thinking that I've gone mad. Maybe I have... bwahahahaha

oooooh, you're working on the same project as me then?

a huge project with recursive stored procedures that return tables that _never finish calculating_ if you don't provide the exact WHERE clause?

where the previous dev thought "i know! i implement my own caching logic, what could go wrong?"

where the 10gb database consists of 8gb logging, of which 7gb is useless, but nothing can be done about it because the customer doesn't approve any improvements they don't understand, and the customer doesn't understand [name a thing]?

where backend-APIs can change daily, and the only time we ever hear about it is when stuff in production breaks because of it? (or rather. has been broken for 2 weeks because of "enterprise processes")

@tosensei holy shit! I think there is a serious word to be spoken with that customer, especialy considering the risk of downtime or maybe dataloss/manipulation.
Fixing such terrible stuff in the "early" stages makes it way easier than having to deal with regular maintenance...

@PonySlaystation trust me, i've tried for years. no chance. i've long given up on trying to improve anything about _this_ situation.

i've switched to "rulebook slowdown"-mode. when they tell me to implement garbage, i tell them it's garbage - once - and then implement it if they still want it. i'm done giving fucks about that project a long time ago.