> PM barges in
> "Have a ticket"
> something breaks in some subprocess at the core of the application
> the subprocess is some deeply intertwined, untested, undocumented, 80 files; all of them write on a globally accessible singleton with a complex system of events and RPC calls
> refuses to elaborate further
> leaves

Oh, almost forgot we have a bunch of setIntervals periodically tinkering with the singleton too, because how the fuck could we possibly miss that one out

@retoor no, that's a normal meme cat I post puff only in comments, upon request. I don't have puff pics at hand as of right now, sadly

also rpc calls over ws is something I actually wanted to try for a while tbh

@IHateForALiving I will second @retoor's WS RPC being amazing, having implemented a client from scratch in node/deno.

Also let me guess the PM was the one who wrote that code originally/senior who left

Time to break into that house with the broken window, shit a huge turd on the floor and run out while ducking.

Ask b2plane for diet advice for best results.

@retoor You're more up to date than you think, knowing how to implement custom web components or the difference between function() {} and () => {} is not that common ❤️

@BordedDev hmm, js "devs" still believe they have invented first class functions?

@Lensflare I'm sure a lot still think it was the first to invent classes/prototypes (and don't realise how much sugar is in that language)

@retoor I can imagine that's a bit strange for people, but that was also a bit of a trend for a while right, trying to mimic desktop style. I've been required to use an old system, and very much makes me think so.

I did a bit of jquery, mainly for the `$` but otherwise not much - must have been an interesting time. Java was what I was doing stuff in back then

Ok, so, analysis: there's at least two files writing on the singleton with the wrong behavior; you may patch one, the other will still write the same thing.

So I need to patch both of them (one is 1200 lines, the other is 1800 lines), and the second is some unreadable clusterfuck of intertwined connections, the current situation being the result of tens of tickets and business requirements nobody ever bothered to write down -a good part of which is entirely lost to time as moving the repository from GitLab to BitBucket lost the history so I can't reconnect any line of code to whatever ticket originated it. There's no way I can touch this shit without us getting sued. Wish me GL.

Ok, so, analysis: there's at least two files writing on the singleton with the wrong behavior; you may patch one, the other will still write the same thing.

So I need to patch both of them (one is 1200 lines, the other is 1800 lines), and the second is some unreadable clusterfuck of intertwined connections, the current situation being the result of tens of tickets and business requirements nobody ever bothered to write down -a good part of which is entirely lost to time as moving the repository from GitLab to BitBucket lost the history so I can't reconnect any line of code to whatever ticket originated it. There's no way I can touch this shit without us getting sued. Wish me GL.

@IHateForALiving good luck, bro!

@IHateForALiving Hey check your local labour laws, in SA they can't penalise you for more than 40% of your salary

But I'm sure it'll be fine, just tell them you've integrated AI and it's still in training (while you're fixing bugs)