You must log in or register to comment.
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.
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.
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.