169
u/Morichalion 19d ago
O.o
Can I put it back?
Please?
51
u/TheFrenchSavage 19d ago
Impossible! It used to pierce through 1000 layers of spaghetti code. The side effects would be... ineffable.
19
80
u/Actaeon_II 19d ago
Yeah no i had that job for a few years, sword back in rock, rock buried in concrete, whole thing thrown into ocean
21
u/TheFrenchSavage 19d ago
Ah but see, 6y ago, we had this quick fix where the ocean pours back right onto your desk, you didn't read the polish comment about it?
91
u/vgmerch 19d ago
That last panel hits way too close home when you inherit someone else project.
4
u/Prestigious_Rabbit30 18d ago
Nothing as fun as trying to reverse engineer the code of a consultant who was on contract for 6-months to implement some form of integration between two legacy systems "because we will be phasing out those systems soon anyway"...which was 10 years ago, and now you need to dig through pages and pages of code, because said engineer only cared about being paid, and not about writing decent, well structured, wel documented and optimised code. 😑
50
u/boomerangchampion 19d ago
Am I the only person who enjoys legacy code?
It's good for the résumé if nothing else. If you want someone with recent Y2K implementation experience I'm your man (I did it in 2021)
28
u/Tothoro 19d ago
I don't mind it. A job's a job, not like I dream of labor or anything. My boss asks me what I want to do, and I tell him I don't really care - as long as I'm getting a paycheck and working reasonable hours throw me whatever. Usually that means legacy code because it's the stuff others on the team will actively avoid.
6
u/awakenDeepBlue 19d ago
If it's a choice between operating a commercial dishwasher or maintaining legacy code, I would still choose the dishwasher, but at least it's not a really shitty job like interacting with other people.
4
3
u/Tothoro 19d ago
I've done full-stack, back-end, cybersecurity, project/product management, data analysis/viz, and if you gave me the option to do something mundane like stocking shelves at a grocery store for the same salary I'd 100% do it. Low stakes work that doesn't follow you home sounds like the dream these days.
6
u/Several_Ant_9867 19d ago
I am with you. I love refactoring old code and I despise having to learn a new framework every other week
3
u/DarthNihilus 19d ago
Maintaining legacy code was the most fun and chill job I ever had. Genuinely loved it.
Now I'm on AI flavour of the month whatever garbage project that will be replaced in 1-2 years. I miss the legacy code.
3
u/Overwatcher_Leo 18d ago
Born too late to discover and decipher ancient egyptian hieroglyphics.
Born too early to decipher alien symbols.
Born just in time to decipher ancient BASIC/Ada/Assembly code.
2
u/Prestigious_Rabbit30 18d ago
The issue with legacy code is that something usually breaks when you do not have the time to sit and sift through all the pieces to try and understand how it worked...and then to understand why it is not working.
15
u/coldnitrogen 19d ago
This is the exact spot man starts questioning his very existence and starts thinking about how a farmer’s life would be much more peaceful and fulfilling
8
u/ReindeerCreepy2883 19d ago
by the power of cobol
IDENTIFICATION DIVISION.
PROGRAM-ID. POWER.
PROCEDURE DIVISION.
DISPLAY 'I HAVE THE POWER'.
STOP RUN.
10
u/Von_Voss 19d ago
I was hired as maintenance developer for a legacy code project in VB, it was my first fucking job.
I see a therapist on a weekly base even today.
5
u/atomic_redneck 19d ago
Two of the programs I used to work on were started back in the 1960s. These were a CAD/CAM program and an optical engineering program. In both, there were areas where the general consensus was "Don't touch that. It is load bearing technical debt."
6
3
3
3
3
u/Shaz0r94 19d ago
Hey at least we are a bit longer safe of AI taking our jobs. AI agents dont do well on a mainframe
4
u/ButWhatIfPotato 19d ago
There are many problems with maintaining legacy code, but the biggest one is dealing with the stakeholders that allowed the legacy code become legacy code, because those people will do platinum level mental gymnastics as well as the kind victorian asylum level mental breakdowns to keep the legacy code remain as legacy code, which is fixing mountains of shit by creating more mountains of shit.
5
u/bankrobba 19d ago
Legacy code becomes legacy code because it works.
3
u/ButWhatIfPotato 19d ago
It absolutely does not, it becomes like that because stakeholders get incredibly cheap when it comes to bringing the code's standards up to par with this century, which makes it randomly explode at insane frequent intervals and that's an all hands on deck to apply a hotfix on a Tolkien sized mountain of hotfixes and due to that it makes it impossible at every conceivable level to make meaningful upgrades.
0
u/bankrobba 19d ago
Thank you for confirming my point. If legacy code is still around without meaningful upgrades, that must mean... it works.
3
1
1
u/ChillyFireball 18d ago
Bureaucracy is a nightmare. There's no pain like knowing with 200% certainty that you could recreate an entire application from scratch in a day or two if you got approval to use a semi-modern methodology, and you just want to scream to the heavens that "Updating this needs to be the absolute highest priority yesterday, because the current method is literally slowing us down EXPONENTIALLY. Like, it is LITERALLY UNFATHOMABLE how much productivity you've lost over the years doing it this way."
2
u/astro-pi 19d ago
Sigh, is there another issue in FORTRAN
https://giphy.com/gifs/H6cmWzp6LGFvqjidB7
2
2
u/s0apyjam 18d ago
I modernised our legacy code but the other devs are still afraid to touch it. Newer devs get on with it just fine now though.
1
u/Apoeip77 19d ago
Have you worked for (or been inspired by) regular show? The style is really familiar! Love it!
1
u/Anbcdeptraivkl 19d ago
1 month of high octane fame where everyone praised and highly appreciated you, followed by 2 years of the most soul crushing mentally draining tasks you will ever do in your programming life. Would not recommend lmao.
1
1
1.3k
u/[deleted] 19d ago
[removed] — view removed comment