Do you have this guy at work? I do

Company’s project is not your project. Don’t get too attached.

Words of wisdom.

This guy is me. Fuck your job. Take all you can, give nothing back.

So... How are things at work?
- Super relaxed, that comes with the territory of not giving a fuck. Also I make good money.

Reminds me of the KSP2 fiasco. Management insisting on reusing the engine from the old game, and firing all the senior devs who could have told them there was no possibility of getting the features they'd announced to work without rewriting the engine from scratch.

It's so sad what happened with KSP2, we were all so excited at the start. I'm glad I didn't buy it though
- It can't be repeated enough: never pre-order a game
- I bought it, learned that there was no career mode and no plan to add one, and refunded it
- I rewatched the KSP2 announcement trailer recently. It's still great, but the song definitely feels more like a funeral dirge now.
They also wouldn't allow the new devs to talk to the old devs, so they had to figure out the old codebase for themselves.

My previous work used two mission-critical software for continuous operation.

One was some guy's university project written in Object Pascal and PHP and largely untouched since 2006. I tried offering fixes (I also knew Pascal), but I was rejected every time because the cumulative downtime caused by software issues was not enough to justify the downtime caused by the update (obviously this was determined by a Middle Manager (derogatory)).

The other was (I shit you not) an Excel spreadsheet with 15000 lines and 500 columns. I tried making a copy and cleaning it up, but Excel couldn't handle the amount of data and ran out of memory.

I absolutely cannot stand this kind of logic.
"We make a shit ton of money on this very critical piece of software!"
"Then let me fix it!"
"NO! It's making us money NOW! It only stops making us money when it's broken. At which point then we fix it."
"But that might be hours. We can minimize downtime if we plan properly."
"But it's making us money NOW!1!1!”
I shit you not I have had various versions of this conversation throughout my career, across industries, across disciplines.
- True zen is achieved when you realize it's not your problem. Even better when the thing eventually breaks and you can be smug about it.
Oh yeah, I remember the good ol' "Our whole business Logic is within this 30 tables spread sheet, that only one person can read, and don't you dare restarting that computer" times.
One person. Sitting in front of three monitors. In front of a spreadsheet that maxed out every resource of that computer. It was glorious.
- don’t you dare restarting that computer
  We had two desktop PCs on the factory floor doing server stuff for a lot of assembly machines. We couldn't move them to proper hardware or virtualize them because the GUI and the server were built as one monolithic application (I still don't trust any Japanese company's developers as a result), so one computer was made the primary server for one half of the factory and the fallback for the other half, and vice versa, to solve the reliability issues stemming from the software's dogshit design.
  What it couldn't solve was Windows' dogshit design. One early Monday morning, when we switched on the factory, Windows decided to force-update itself, then failed and bricked both computers. We spent half the shift with our thumbs up our asses periodically checking if tech support bothered to show up yet.
- It sounds glorious!

"Every dependency is an asset. Every dependency is a liability."

Sums up every Node project I've had the displeasure of looking at. The lock file being the only thing holding the twisted web of versions keeping that franken-app running between a minefield of incompatibilities and buggy hacks.

*laughs in wordpress*

ffs, every time someone from a community group asks me "Can you have a quick look at our basic website, we just need to change
<reallySimpleThing>
", and I'm like "sure, i used to do web development, let's have a look [...] FFFFFFUUUUUC...."

Dude, I'm so bad at arguing in zoom so the guys that push for that shit get their way. Fml.

Have you considered you're just bad at arguing in general and it's not the medium?
- Difficult to punch coworkers in their face in zoom

I have a coworker who thinks I'm this guy cuz it's apparently absurd for us to add the 5 most popular dependencies on the planet to our environment and I'm sentencing us to the doom of dependency hell.

Yes, most of my jobs have had people who take vacation.

Oh I hate that

That's me

Personal projects = it'll work until it doesn't
Professional projects = I'm hiding in the MDF hoping no one finds me

So you use SharePoint as well? Hahaha

Sure, but refactoring things constantly leads to bugs too. Once it works you should stop rewriting code. The SW team at my job didn't get the memo.

Refactoring is often necessary to ensure new features can be continuously added with ease.
- Yes, and you do it at the point you need to work on that feature. The business pay for it when they want the change.
  You do not pay for the refactor with your time, if the company won't pay to fix their code. Just make it clear the risks and how bad it could be if you carry on with duct tape fixes.
  You have to be strong and firm and not agree to hacks. You need to work with your team to ensure you're on the same page rather than getting undermined by cowboy dev claiming he can do the feature in 2 days when it needs 2 weeks to do the necessary work.
- Sure, refactoring is sometimes necessary. But refactoring also introduces new bugs often. Our code base is constantly being refactoring, and it's not more reliable, stuff is constantly breaking.