Everyone here ranting about a fucking missing semicolon. I can't remember the last time a missing semicolon was the issue...

You wanna know what's REALLY BALL-BUSTING????

WHEN THE FUCKING 10 y/o LEGACY CODEBASE, CODED BY FUCKING PHP WORDPRESS SCRIPTERS WHO THOUGHT THEY COULD BUILD AN ENTERPRISE SHIT CAUSE ZF2 "LOOKS EASY" AND THEN FILL IT UP WITH SPAGHETTI, IS SO BAD WRITTEN THAT IN ORDER FOR THE PAGE TO RENDER YOU ACTUALLY ****HAVE**** TO DISABLE ERROR REPORTING SO WHENEVER A FUCKING ERROR HAPPENS ON THE TEMPLATE RENDER COMPONENT OF ZEND FRAMESHIT 2, YOU'RE LEFT WITH A FUCKING BLANK PAGE AND NOTHING IS LOGGED TO THE LOG FILE, SO YOUR ONLY OPTION IS DIE() DEBUGGING LINE BY LINE ON THE 1300 LINES PHTML FUCKFEST OF A VIEW THEY HAVE.

MISSING SEMICOLON? YES PLEASE, GIVE ME MORE OF THAT SHIT

I've learned that trying to jump into a project without properly understanding everything it will entail is bad.

I recently worked on a project that involved modernizing a legacy system and no one on the team (including me) fully understood how the legacy system worked. This led to us missing a lot of edge cases and attacking the project in a way that really wasn't beneficial overall.

If we had thought about the entire system beforehand and mapped out the legacy system, the project would've turned out much better.

His legacy lives on
Rest In peace

My team: gets fired

8 other colleagues: here’s our notice, we leavin

Love it, they’re left with 4 devs so good luck finding people who know how to work in your 20 year old legacy that every app in ur company is built on lul

Costumer: I found a 40 line python script on Stackoverflow to do that.

Dev team: ok, now... how many lines you think we will need to put the python interpreter, libraries and your 40 line script inside an Android and iOS apps with legacy code?

I got a work on legacy code. The app really depends on a library that was last updated on 2009. The website docs also missing

RIP

A person may die, but an idea lives on forever. That and extremely shitty legacy code.

My teammates are working on a legacy codebase so shitty awful, so poorly written, so full of pitfalls, hidden information and intricate relationships, they gave a name to their development style:

Indiana Jones programming.

After our Head Of Software has terminated.

I started to take control over our development crew. And in this year I did more then the old head in the last 6 years.
- Swapped from plain old SVN to Gitlab.
- Build a complete autonomous deployment with Gitlab.
- Introduced code reviews.
- Started to refactor the legacy product with 500.000 lines of code...
- learned how to use confluent apache kafka and kubernetes to split the legacy project in many small and maintainable one.(not done yet)
- Last 3 weeks I learned how to use elasticstack with kibana and co. That we aren't blind anymore. Big dashboards are now shown in the middle of the room :) and maybe convinced my coworker that we use unity3d for our business application cause of support for all devices and same design on them. And offline capabilities. (Don't know if this was my best idea)
When I look back, I'm proud to did that much in one year alone. And my coworkers are happy too that they have less work with deployments and everything.
But I can't decide what's the title for this. System or Software Architect cause I litterallity did both :/

If you thought your legacy code was bad, this is what I'm dealing with. The below SQL is stored in a cookie on login and executed to on every further request to determine the user / privileges.

This bitch at work is afraid of hard work and is currently spending more energy fighting the work than just doing it.

She wants to keep a legacy setting that's on the wrong scope -- per merchant, not per payment -- in addition to the setting I've added on the correct scope. She's bringing in management two levels up all because "I've already moved on from this" and "it will require me to write code quite a bit" (first paraphrased for clarity, second is an exact quote)

Bitch, your way is dirty as fuck and is going to break things. Roll up your sleeves and do your damn job!

I just got handed a legacy php web project... Full of vulnerabilities... And it's using only mysql_ functions... Not only it's not OOP, there is not even a single class...

How good it's coded: User profiles are created manually by the frontend dev as htmls, and then the past php dev implemented them as links etc in the current page.

This is how I feel:

I can maintain your shitty legacy node 6 code
And the shitty m3 ec2 instance with Ubuntu 16 that it runs on
And another one with postgres 9
But if I have to make a powerpoint presentation, I am jumping ship.
A man has his limits

Big thanks to the guy who blamed the poor structure of a legacy database on me today because I'm young. You made my day

So many moments like this working on the legacy code at work

just another day at office working on legacy code.

Me when I get put on a legacy system maintenance project

Always take the challenge.

Didn't know front end - took tasks that were front end oriented, took me longer but I learned.

Didn't know what goes on in the legacy code - took the tasks and dived right in the filth.

Fear the day the challenges will be over.

Debugging vb code written by someone else, on a lagging remote desktop connection

I guess this is the peak of legacy code

Was working in small startup with great people on new projects, but for very low salary and shitty conditions.

Changed job to big company with nice salary and great conditions, but people are assholes and have to work on legacy stuff mostly.

Guess you can't have everything.

Was updating a legacy website when I came across this gem... Gotta wonder what was going on back then

Fuck all this legacy shit. I'm buying a strip club on the bahamas, seeya!

In the span of a week, I:

* broke up with my girlfriend
* had to make a site go live for a client that wouldn't fucking cooperate and give me what I needed to get the fucking site live
* was given legacy code for a wordpress site that looked like what a fucking brainless monkey would type out by smashing its head repeatedly on the keyboard.

It can only get better from here, right?

-When they ask for your current/previous salary in a job interview, tell them that you don't find that relevant or that you don't want to tell. If they insist on you telling your salary, GTFO

- When they are overenthusiasticly telling about all the latest technologies they're using without staying one word about legacy projects, GTFO. It's a trap.

- If you walk trough the developer room(s) and everybody is extremely focused and just programming like a zombie, GTFO.

- If they cannot tell you one single downside of the company, it's probably too good to be true.

That's about everything I can think of at the moment

I just discovered a local beer brewery called Crazy Duck. Now that's my kind of debugging buddy!
I'm buying some the moment I get back from vacation to test them on a legacy PHP project.

Legacy code.

Honestly though, this is some of the better legacy code I've worked with at this company. It's a nifty alert system wherein you can trigger sending messages to subscribers of that alert via whatever means (phone/email) they've entered.

I'll save you the technical analysis of its internals, but suffice to say it's actually pretty nice, with good separation of concerns, internal logic hidden away, dead-simple public interface, etc. documentation is kinda crap, but it exists (!), so that's a nice change.

but.

For some unknown and bloody bizarre reason, the thing breaks when a user wants both sms AND email notifications. Either by themselves work totally fine, but both together? nonono. Email alerts give ArgumentErrors, so something internal isn't correct, and SMS alerts complain about uninitialized Twilio::Error constants.

but.
they both work fine otherwise?

also, the two notification preferences aren't stored on the same object anywhere. if a user wants both, the user creates two AlertContact objects with different info, and when performed, the Alert basically iterates over these and does its thing for each, so there is no knowledge shared between them. totally should work the same regardless.

idfgi.

ALSO.
AND THIS PART REALLY PISSES ME OFF.

WHEN THERE'S AN ERROR, THIS THING DOESN'T LOG IT. IT STRINGIFIES THE ERROR OBJECT (basically just extracting the message) AND INSERTS THAT INTO THE DATABASE INSTEAD. WHAT THE CRAP.

So, I don't get a stack trace, line number, or anything. just the basic error message. instead of my alert text. because of course that makes sense and totally helps debugging.

aklsjfak;sldfj.
legacy code.

Spend several days decoding API legacy code from the guy who got paid shitload of money and then stumble on the piece of code that shows he isn't even aware there is a count function in SQL (or rowCount in PDO)

:)))))

So I had a fun week.

It started off with my boss replying to a co-workers email where he sent his new bank account, saying he doesn't need it untill we close off some baddly planned projects, meaning no paycheck.

Needless to say we were working night and days including weekends on it and put our best into it.

For the next part I need to explain a little background. We have this old legacy system I'm working with for the past 3 years. I keet raising the red flag we need a new one. Nothing happened. So every time I worked with it I kept thinking how to improve the parts. Almost two years went into thinking and planning the new system untill I got a green light. It was most satisfying - the day I got to build something good and awesome. I drew all the data structures, laid out the foundations and started building ontop of it. It was amazing and I was really proud of it. Then suddendly client wanted to see something and the decision was made we threw it together quickly with the old legacy system. It was on hold 'till then due to work overload.

Boss wrote me this week if I can put the project from git on a server, where he out sourced the completition into India where they will finish it. On thr question if they can't work on git, he replied: "should they?" -.-

To top it all up, I got a notice at the end of the week if I don't fill his shit time tracking system (that takes me one hour/day to insert all entries) by monday he'll deduct a sizable portion of my paycheck.

I AM WORKING FOR YOU ALL THE FUCKING TIME BECAUSE YOU LACK RESOURCES AND I THOUGHT A TEAM STICKS TOGETHER AND SAVES EACH OTHERS ASS! I DONT HAVE TIME TO ENTER YOUR FUCKING STUPID TIME ENTRIES IN YOUR FUCKING BUGGED SYSTEM EACH DAY ON TASKS THAT DON'T EVEN EXIST BITCH! MAKE IT BETTER FIRST!! OH! AND NO ONE IS MORE QUALIFIED TO FINISH THAT PROJECT THAN ME, I POURED MY FUCKING HEART INTO IT YOU PRICK!

woah.

I'm Working on a legacy app in VB and I start to like it.

I need help, this is not a meme.

When the last dev wrote code and you dared to read it....switch on a Boolean, what even is your life legacy dev?

I love how the Keybase Linux client installs itself straight into /keybase. Unix directory structure guidelines? Oh no, those don't apply to us. And after uninstalling the application they don't even remove the directory. Leaving dirt and not even having the courtesy to clean it up. Their engineers sure are one of a kind.

Also, remember that EFAIL case? I received an email from them at the time, stating some stuff that was about as consistent as their respect for Unix directory structure guidelines. Overtyping straight from said email here:

[…] and our filesystem all do not use PGP.
> whatever that means.

The only time you'll ever use PGP encryption in Keybase is when you're sitting there thinking "Oh, I really want to use legacy PGP encryption."
> Legacy encryption.. yeah right. Just as legacy as Vim is, isn't it?

You have PGP as part of your cryptographic identity.
> OH REALLY?! NO SHIT!!! I ACTIVELY USED 3 OS'S AND FAILED ON 2 BECAUSE OF YOUR SHITTY CLIENT, JUST TO UPLOAD MY FUCKING PUBLIC KEY!!!

You'll want to remove your PGP key from your Keybase identity.
> Hmm, yeah you might want to do so. Not because EFAIL or anything, just because Keybase clearly is a total failure on all levels.

Written quickly,
the Keybase team
> Well that's fucking clear. Could've taken some time to think before hitting "Send" though.

Don't get me wrong, I love the initiatives like this with all my heart, and greatly encourage secure messaging that leverages PGP. But when the implementation sucks this much, I start to ask myself questions about whether I should really trust this thing with my private conversations. Luckily I refrained from uploading my private key to their servers, otherwise I would've been really fucked.

Yo, is this devrant or spamspace???

Like, do you even fucking work, mates? Are you a dev? How doesn't a fucking legacy code piss you off on a daily basis? What are all the ways you want to respond to your customer's/PM's abuse? Does your lead dev even know jackshit?

Where did all your quality rants go? Why do you all sound like second graders writing essays for school? Have some passion for your job, and hatred for the incompetence for others!

Now, go produce some quality rants! Funny ones too! Bonus points if it's angry-funny.

Oh boy, my riskiest coding decision was certainly that one time when I refactored some 50k lines of critical legacy shit code in 3 days, straight up merged everything into master and then deployed to prod.
Luckily there was only one minor bug I had to fix after that... phew...
(To my defense: I was solo-working on it - the infamous CMS Of Doom™)

Another non programming related rant although kinda tech related.
So I work in a distribution center and today I learned box packing.

1. THEIR LEGACY ASS SYSTEM ONLY RUNS ON IE (FUCK ME IN THE ASS SIDEWAYS PLEASE).
2. SYSTEM CONSTANTLY FREEZES.
3. THE HAND SCANNERS RUN ON AN OLD FUCKING LEGACY WINDOWS (PRE 2000 I THINK) SYSTEM AND IS SLOW AS MOTHERFUCKING HELL.

Yes, it is VERY frustrating to have to work with this FUCKING SHIT THE WHOLE MOTHERFUCKING DAY.

Plus side today, the locations I had to pick from today included 200, 403 and 404. Had loads of inside jokes about not being able to find locations and not having permission etc 😆

Me fixing bugs on our legacy system

Before starting a job at company CUNT, we had an interview at which I told them I do not want to work on legacy monolithic codebases. We had a nice agreement and they offered me to work as a back-end with one of their projects. I was super excited to start. CUNT was very culty, always talks about how carrying for employees they are and always keep promises on their end of the table.

A week has passed, the codebase is superb legacy shit hole, no fucking standards, monolithic as fuck (BE and FE projects live in one project folder with tons of depreciated tools - there are no docs for them. That’s how old they are). They even have secret folder in their project with YOU GUESSED IT - secret keys.

Told CTO today, that I want to switch projects, because this was not the thing I signed up for and remember THEY ALWAYS CARE ABOUT THEIR EMPLOYEES AND PROMISES MADE. He basically told me, that project owners (other company) will not understand this culturally and I can either wait it out and possibly get my hands on a better project or fuck off right now.

Also, I was told, that my judgment was garbage worth and I should work longer with project “shit hole” to fully understand it.

Such a fucking salesman.

Anyways, I told that this situation is not culturally appropriate for me either as they gave me a sort of promise and I wont leave the company as I just switched jobs and cannot afford to do that again. I’ll hopefully get another position in another project soon.

WTF IS WORNG WITH PEOPLE

Based on how many people are violently upset at Apple for removing a 60 year old piece of technology from their phones I'm guessing this is the ideal types of ports for some people. Because why try something new when you can stick to legacy technology?

So I watched this video that tries to convince people, that the jQuery library isn't really best practice anymore and showed how you can achieve basic tasks with vanilla JS, aswell as some frameworks (Vue, React, Angualar) and how they handle interactions with the DOM.

It also talked about how nearly every JS question on SO has top answers using jQuery, and how that's a bad thing.

But what I found in the comment section of this video was pure horror: So-called "Developers" defending jQuery to the death. Of course there were some people who made some viable arguments (legacy code, quick & dirty projects), but the overwhelming majority were people making absurd claims and they seemed quit self-confident.

GOSH!

Want an example?
Look:

On the first day of Christmas, the bossman gave to me: The fact that my new computer purchase order needs to be OKed by the CEO and I need to continue working on a 2014 Mac Mini (i5-4260U, 8 Gig RAM, GPU shot by an ESD on the case long ago) for the next year.
On the second day of Christmas, my family gave to me... a good reason to get shitfaced
On the third day of Christmas, getting shitfaced gave to me: A hangover and some urgent plastic welding job that had to be done with a soldering iron. FML, I've had a headache before breathing in pure hydro-cyano-whatthefuckyougetwhenyoumeltplastics
On the fourth day of Christmas, my team gave to me: A legacy, age-old Rails 2 project that was written by an intern and never reviewed, went to prod in 2014 and can't be changed anymore, but needs to be changed after the fact that it has zero test coverage and needs 100 % now to prevent issues and costly manual testing.
On the fifth day of Christmas, devrant gave to me: The Idea that making fun of Christmas songs to get over the sheer amount of dicks that working over the twelve days of Christmas sucks.

To be continued...

How I spend my days at work working with legacy code:

* Writing tests before I do anything
* Noticing that i cannot write tests because of antipatterns. Lots of them.
* Refactoring to make at least a tiny bit testable.
* Then writing tests.
* More rewriting and refactoring
* Finally adding that one feature my boss asked me for
* Writing tests for that new feature (my do that before implementing)
* Explaining to my boss why it took me so long and agreeing on stopping writing tests.
* 2 days later: explaining why i still broke something.

But in the end my code works just fine.
my colleagues handle things differently. They just ignore problems as long as at least one feature works a bit.

I've taken over a project with legacy code, this is one of the methods:

private bool areEqual(string value1, string value2)
{
return value1 == value2;
}

Also, the opening brackets are on a new line

[CMS of Doom™]
The gift that keeps on giving...
When you think you've seen it all after 7 months in legacy hell, you get another gift:

Let's say you use PHP, but your IQ is in the zero-ish range, then it is obvious to:
- use define() for constants in all your config.*.php files
- then include said config.*.php files multiple times
- and because define() doesn't overwrite the same constant, because it's - you know - a constant, you instead of including just do a file_get_contents() to read the PHP file as string and then parse the values by Regex.

The dev who wrote this was truly one of the devs ever.

working on legacy code and saw this:

@records = unpublished_collection.published

Wait, what?

My company just got a new developer to work on a legacy PHP app.

My boss was boasting about how this guy has more years of professional experience than me ( I have 9 months of experience and he has been working for 4 years on PHP).
Today was one week since he started and I had him set up a REST API, I had to explain to him what json_encode does and how http requests work.

My own personal hell was a html page that had a script tag that called a rest endpoint that sent back a text block of JavaScript that was then dynamically executed to redirect the user to a php 3 page that was the exact same thing as the original page but with an extra bit of css to make the buttons blue and slightly rounded

You can’t make this shit up

*edits file on remote server*
WanBLowS: naah you can't 😈
*le wild BSOD appears for the over 9000-th time*

... Yeah. Windows, great job. Who needs system integrity when they're working on remote servers anyway, right?!

And to top it all off, le reboot mentions that they're working on fucking "features" again. That's what you needed to BSOD for?! For a goddamn motherfucking feature?!! Fucking piece of shit.

At least when I opened vim on that server again, it's saved everything neatly in the .swp files, ready for recovery. Now that's neat, isn't it? Microsoft, the Linux community has already moved on to nvim in terms of development, but maybe, just maybe, you can learn a thing or two from our "legacy software", vim.

As for me, maybe it's time to take out my Arch laptop again. At least that won't crap out on me because the sun and the stars are in a position that the OS doesn't like, or something stupid like that. FUCK YOU MICROSHIT!!!

Having pets is a good way to prepare yourself for working in a brown-field environment.

When your cat or dog shits on the floor, you get the same feeling as when you need to dive into a legacy code base.

You know you can't just leave it there, and yet you still want to find anything else to do except for touch the pile of shit in the middle of the room.

Meanwhile you know your users are going to end up trampling over it and mashing it into your carpet.

Tonight, my long-time friend died. He was living in the basement for years, always reliable, always at my service, keeping my files, watching for my git repos, being my private cloud, and so many things more.

He wrote his last syslog entry at 0:21 a.m., passed away and never woke up.

I found him cold and motionless this afternoon, but could not do anything. Any attempt of reanimation failed.

Goodbye, little BananaPi, fare thee well, and if for ever.
I promise you, your legacy on SD card will live on with a new board.

Today I started work on a new project that contains a lot of legacy. I asked the developers about unit testing javascript and was told that not only is there none in place, but it's not worth adding any in.

At first, I grimaced and thought fair enough. This is their codebase, it's their choice. I've now been thinking about this for a few hours and have instead decided that screw those guys, I'm adding in a testing framework, a module pattern that's compatible with the existing code, and unit testing the crap out of it. If they don't want it they can refactoring it out, but I can't bring myself to intentionally deliver code I know is crap.

I WILL FORCE CODE QUALITY ON THEM.

Worst technology I've ever worked with?

Microsoft-FUCKING-Access

The error riddled, varchar frenzy, disgusting ui, os and architecture dependent pieces of shit, powered by the cherry on top: fucking VBA, that are applications developed with this monstrosity have kept me awake trying to understand why on earth would anyone that is not dying of cancer already would use such thing to try to build anything.

I had to deal with load of Access applications when I first started at my current company. Whats left now are mainly legacy systems, I killed them one by one and whatever's left will suffer the same punishment.

If you develop in Access you're my enemy and I will destroy you.

Fun drinking game: work on a legacy system for a few hours. Every time you say "what the fuck?" equals 1 shot.

!Rant
Finally I'm having my vacation. Goodbye mother fucking legacy system. Hello pet projects and gaming. God, have mercy on the lost souls at work ;)

Great. Just FUCKING great. When I was looking at devrant, suddenly some add-ons crashed (correction: ALL add-ons crashed!). All other tabs flooded with ads. I go to the add-ons manager, and what is their SHITTY excuse?
"Starting in Firefox version 57, only extensions built using WebExtensions APIs will work. Not sure if your add-ons are affected? See Firefox add-on technology is modernizing and these Frequently Asked Questions for details."
Anyone of you fuckwits ever heard of LEGACY SUPPORT? Leaving some time so the other devs can adapt to your new brainfart technology?! Even fucking C++ has that. FUCK!
Thank god devrant doesn't have ads.

So I got my internship grades today... The fucking bastards gave me a 16.8 out of 20 when I had to work my ass off on legacy VB6 code, using poorly documented add-ons and barely asked for help. I always tried to figure things out myself and that helped me learn that useless crap. But they rate me that low after all the effort I put into a payless job?

So you mean that not only was I not paid, they were also not thankful for said unpaid job. Fucking waste of half a year.

Often when I struggle with a complex programming task or get stuck in a bug, this cube and a big cup of ☕ helps me to get back on track.
But when nasty legacy PHP code or WP templates hits the fan, only a mental institution can help...

Your favourite comment?

My team was working on a legacy system, one part of it is an assistant, sadly required as global variables.

Being a non-english-first-language company, some dev years ago thought shortening said assistant to "ass" would be a wise idea - less to type, right?

When we redid the application 2016 part-by-part, our code needed to define 3-4 global variables starting with the "ass" prefix for the legacy parts to work. The colleague who was tasked with this is a fine gentleman from England.

Later as I read through the commit, I found 5 lines of code following 20 lines of comments explaining and deeply apologizing for "ass", "ass_open", etc.

The same dev also had a "HACK OF THE YEAR" comment he moved around when time constraints made a less-than-optimal fix necessary which was worse than the last "highscore".

I consider just strangling somebody because iOS14 fucked all legacy Google Cardboard SDK apps overnight.

8 months already, still can't get all my old apps to work, for a thousand reasons.

If I didn't know better, I'd sue somebody. But it's apple, and I'm not Epic, so fuck me.

"Ohh dude why dontya just rewrite your apps to support Unity XR? hurr durr easy peasy lol so cheesy"
I'm tryin, but it's so underdeveloped and featureless, that I need to rewrite and create everything, and in some cases I can't because old apps had many dependencies. I am porting all my prefabs for hundreds of unpaid hours over the last 3 quarters already, and keep getting stuck.

Today I just extended an 8th deadline set by my clients. Each of those are exponentially more explosive and demotivating. It's not just the question of losing money for them - some of their careers depend on these apps I had made. (Long story, but it's exactly like that)

WHAT HAPPENED TO MAINTAINING LEGACY SUPPORT?!?! Nobody asked anyone to deprecate perfectly well working gyro/accel api on all <5 year old iPhones overnight TIM.

My client's using some legacy server side software. I set it all up nice and isolated with proxmox, tunneled it through cloudflare, got the folks to do their install on a windows vm, passthrough their licensing usb. Hosted GLPI on it too (system inventory) and so on.

Wait for it. Windows Server refuses to accept local or domain passwords. WTF. Even went ahead and did a Utilman reset on it which lets you use an admin cmd prompt to the login screen where you could reset the password. Insane that it was even possible, but no good.

Client blamed linux for it, I switched over to Windows Server on baremetal. I setup Hyper-V thinking it should be just as capable as KVM.

Nope.

Guess what, you can't pass through usb for licensing (the legacy software). MOFOS DECIDED TO install it baremetal. I couldn't even get hyper-v to create a decent virtual network. It keeps changing all my network adapter settings. I COULDN'T EVEN PASSTHROUGH PCIE NETWORK CARDS.

This feels like an eternally stagnated, mossy soup of abandonware.

FUCK YOU WINDOWS. You've been sore pain the ass for EVERYONE.

RIP Dr. Larry Roberts, who helped found ARPAnet and the internet. Your legacy will live on well into the future.

I love Test-Driven Development!

And because of that fact, my heart shatters into thousands of pieces, when I recognize error events on our production nodes which are pointing onto a golden hammer function in a legacy project.

This particular function has about 300 lines with a bunch of subfunction calls and instantiations of helper-classes returning information for workflow.

Refactoring this code to apply proper unit-tests requires a way bigger investment than simply deal with 30 eventlogs a day, because this kind of payment is barely used by customers of our webshop.

This fact is a little itch each day of my work.

Guess it will make me go insane one day
¯\_(ツ)_/¯

xD

Okay, first rant here.
Spend most of my morning searching for a js file that was supposed to build some graphs in a report page in this legacy system (still in active development) just to find it embedded inside a random .php file being included inside a wall of if-elses (that shit has around 100 lines) on the index.php (that somehow manages to route all the nonsense that's going on there).. was it really that difficult to make it a proper .js file? and actually import it on the page that is using it? c'mon...

It's 5 AM and I don't want to shit on anybody's party but trust me when I say most of you here complaining about legacy code don't know the meaning of the word.

As someone who maintained a PHP4 codebase with an average file length of 3000+ lines for almost 4 years, I feel you, I feel your pain and your helplessness. But I've seen it all and I've done it all and unless you've witnessed your IDE struggle to highlight the syntax, unless you had to make regular changes in a test-less SVN's working copy that **is** the production and unless you are the reason that working copy exists because you've had enough of `new_2_old_final_newest.php` naming scheme, you do not know legacy. If you still don't believe me bare in mind I said "is" as in: "this system is still in production".

But also bare hope. Because as much grief as it cost me and countless before me, today of all days, without a warning, it got green lit for userbase migration to a newer platform. And if this 20 years of generous custom features and per client implemented services can be shut down even though it brings more profit than all the other products combined, so can happen to any of your projects. 🙏

Unfortunately, I do mean *any*.

Meeting with a co-worker who is supposed to do a code analysis on a large legacy project. Actually, HER project - she inherited it already years ago, and the original devs aren't in the company anymore.

Her: customer is asking this and that analysis.
Me: easily two weeks.
Her: but who will do that?
Me: you of course.
Her: but I don't know most of the code.
Me: me neither.
Her: and I don't know the protocols.
Me: google them. I'd have to do the same.

Really, I told her to google shit, which I consider as quite a slap for a co-worker. Basically, she tried to offload a complex analysis because she just wants the low effort parts of the job.

Won't happen. DO YOUR FUCKING JOB!

Boss: some consultants worked on this feature extending some legacy code
Boss: it's 90% done
Boss: they used FTP. It uses iframes and we fired them when they couldn't get the frontend modules working in sync with the backend.
Me: git checkout -b herewegoagain
git diff-tree --no-commit-id --name-only -r 666w3wl4d
*copy output list of files to sublime text 3; select all lines; add to each:
gitk --follow [filename] > src/.notes/herewegoagain/[filename].diff
*examines....
Me: It's -10% done. you'll know I'm almost done when I enter the fugue state. You'll find me at this address. Give me this USB stick and a 4 pack of redbull and I'll do the merge.

[...] great! Nice to hear from you that you've got experience using C#! Our shipping company will also need a mobile interface for our IBM AS400 relic older-than-the-pyramids server, can you do that?

Me (a little displeased about the idea of working on a pre-existing legacy server): yes sure, I'm working on a Android project right now, so I'm learning a lot about it lately, I think it's totally feasible

Them: oh, but we are using a windows mobile device

Me (wondering why they are still using Windows phone): I can look it up and let you know btw

> Windows Mobile /= Windows Phone
> Deprecated since 2010

I'm fucked.

Team of developers suggest one of our legacy services is a nightmare to maintain, terrible to develop on top of and is fundamentally wrong in terms of data and application structure.

They are 100% correct and I fully endorse their request to redevelop it.

I'm less enthusiastic that their new version is much worse than the original...

Legacy projects are cancers of this profession. I would not wish maintenance of legacy code(written by someone else) on my worst enemy.

Stupid piece of legacy shit needing to silent print without the dialogs in IE on windows 10.

this is proving to be a thing of nightmares.

this has worked for years but no windows need to block this “for security”

windows and security - i would laugh but this is going to keep me awake at night.

When your boss tells you to work on legacy PHP4 codebase...

Overwhelmed by a shitty codebase? Use the boy scout rule and leave the code you're editing a little better than you found it.

Worked wonders for me when I realized I could spend literal months refactoring and desperately needed a systematic approach.

Little by little that rotting house of cards will turn into something okay. It's a nice feeling looking back after a couple of months and see what you've done to make things better.

Also, make sure to remember the cost of wrestling with hurried legacy solutions in your estimates as well. Just adjust the level of bluntness depending on your work environment: admitting that things can/need to be improved can be unpleasant for some to hear even though it's true.

Worst legacy experience is when you go back to a project you were working on when you first started learning. My own code disgusts me the most.

Today is my birthday and my company as a present will make me work on disgusting legacy code, stored procedures, impossible to debug and convoluted as fuck.
And everything needs to be released yesterday...
Happy birthday motherfucker.

Company wants me to give a rough estimate of developing a new feature in a distributed legacy monolit. They told me they would inform me the next day and want the estimate on the same day for a project that will probably take 2 devs 3-4 months. I ask for more time and info, give the estimate and they say it "feels too much". I mean ok. Then why am I even estimating? If in the first place the client has only X money than do the project for X and it doesn't really matter how much work it is, does it?

Problem: ugly-ass php spaghetti code that has a technical debt of 16(!!!) years. I mean, it's so spaghetti that has two legacy frameworks that talk to each other inside the same monolith.

Observation: after two months my colleagues, trying to refactoring stuff, they were able to touch so little stuff that it almost made no difference.

How much is worth a rewrite? Because i don't think i can make a difference on a codebase so messy.
I know that rewrite is not the answer 99.9999% of the time, but i have tons of doubts here.

(As a freelancer I was asked to do a couple of tasks on legacy code)

Let’s check this code, how bad can it be?

- all of the following: unreadable mess, no auto linting

- tests: some are there cause there’s not enough automation, others are poorly named
- frontend: somehow a genius made a react component for every variable in the store which only passes the variable to the child (wtf)
- backend: death by best practices
- ci/cd: “we have it but it’s broken”

Let’s fucking goooo 😎

Diagnosis: my therapist is getting rich
Chances to not cry tonight: close to zero

At least they pay well 🤷‍♂️

The first two stories on slashdot's homepage are:
1. Google releases Angular 2, breaks backwards compatibility
2. Apple releases Swift 3, breaks backwards compatibility

If you use either of those tools, why do you put up with this? When did software engineering stop being about building useful or enjoyable things for our customers, and start being about doing thankless make-work for Silicon Valley billionaire companies? Is this the legacy we want to leave to the world?

Clown manager put three juniors (and ”senior” dev on work visa) on new project.

They will never finish it.

It’s too hard for them with some legacy dynamically created complex database queries which will spook the hell out of them!

But managers like, ”it’s going to be good” and ”making good progress”.

Fuck no! Putting juniors together? With little support? It such a waste. They spent weeks just to get even the slightest progress.

No best practise. No tests. Just hacking away.

It’s a failure of the management! We fail our juniors and they will quit as soon as they get the chance and they feel like they have some wind under their wings.

”It’s going to be good”

Pff. Clowns leading this company.

Sometimes my boss wants me to fire a bullet without a gun, they want me to throw the bullet so hard that it feels like it was shot via a gun.

Maintaining a legacy app sucks so bad when you don't even have the full codebase and some douche bag decided to just randomly throw the codebase on the fucking SVN. 😠

Damn I'm pretty hard hitting my limits here

My company asked me if I would like to work some extra hours because otherwise they don't make all the deadlines

But damnit asking 10+ hours a day from a junior web developer is quite a lot

😒 Especially if it's an old legacy project where I have to work on...

The feeling when you realize some people on the project are writing legacy code from scratch. Apparently it seems they've never heard of any coding standards, they think clean code and style guidelines are for the weak and single responsibility means one single method is responsible for a bunch of unbelievably diverse things. They are like the Gumbys of the dev realm but it's my brain that hurts every time I have to deal with their code.

Some people are really getting high on this Agile shit. Probably because they learned some new bullshit bingo phrases - and it suits them: lots of vapory talk and expensive meetings and others will have to do the work anyway, while they can circlejerk on how to have shorter iterations to improve the time to market, increase the business value, inspect and adapt to faster deliver a minimal viable product - yeah, do the agile transformation, update to the digital age, you noobs. Throwing around some catchy phrases will let you compete with Google? Maybe need some blockchain or machine learning?
While you are clustering your post its, the coders who keep the ship afloat, sit in their legacy code base that's so bitrot they are mainly doing bugfix releases without a single feature for three fucking years. Consider this.

Today I decided that from now on for all strings that need to be initialized and don't need a special value, I will assign a TIE-fighter "|-o-|".
That will be my legacy.

So I found some weird library included in this legacy code, didn't really get what it does and why it's there though.

Turns out there's nothing to be found on the internet about it. Absolutely nothing.

So after browsing through the directory structure a bit more I discover a README file. Hoping for answers I opened it, only to find this...

The legacy codebase, episode 4584985948:
- outdated comment
- die parentheses space string no-space parentheses
- die AND exit, just to be on the safe side
- won't comment about the screaming boolean
- at least they used triple equals (and yep, that's a font ligature)

We've got this legacy PHP system that doesn't really run anywhere else than on it's server. It's not configured with git, and there's no pipeline. Just plain old SSH. How would you go about managing it?

Imagine updating a legacy web app and the code is so bad it physically makes you sick every time you look at it. Tables with over 400 columns, . And don't even get me started on the security issues. Apparently writing "Confidential" on the top of the page is enough security. And that's just the tip of the iceberg. People should get licenced before being allowed to code.

He was brave enough to out his name on this... Legacy code, always full of surprises.

being forced to perform a major version upgrade on a legacy service that your team doesn't own

fml

This is a true story. We had this subject, called “Web Design” (really, “design”), where we studied HTML, CSS, JavaScript, PHP and MySQL (confusing, right?). And when we get the PHP (e-)book, it was this old PDF (probably downloaded illegally) teaching the legacy 4.0 version of PHP. Anyway, when we had to develop the final project, the sane professor allowed us to use a newer version of PHP — 5.2, released on 2008. I had to follow the rules, so I developed probably the less secure web application I will ever develop. That means no protection from SQL injection, XSS vulnerable and a bunch of other security holes… And that’s how they liked it developed!

Legacy code huh?
Well i'd say it would be when i was workng on an old java app that was apparently written by a retard.

He had used strings to represent booleans for no apparent reason. As if that wasn't bad enough he would use different strings too:
Y N true false 1 0

He used them randomly too , y and 0
N and true
😡

I sense it was done on purpose
Perhaps he knew he was leaving soon

So Docker Desktop only runs on Windows 10 Pro. Unfortunate for Windows 10 Home users that comes installed with their laptops like me. Gotta install the legacy Docker Toolbox

Ok, so one of the oldest guy is leaving from my company (on a good note) and he was involved in multiple things in our organization. From having access to almost everything (AWS, Github and owning multiple projects and our legacy code). I am supposed to take KTof one project and man THE CODE IS MESS. YOU DONT PUT A RANDOM NUMBER WHILE CALLING A FUNCTION. You are supposed to define a constant and use that. I've told my manager that I need at least 1 week just to improve logging.

Our ticket tracking system and our IT service request system are from two different companies that are direct competitors. The source code is full of temporary hacks to just make them play nice until a better solution is worked out. Fast forward a few years and we're abandoning both systems in favor of a single, unified system that handles everything. We currently have maybe 20% of the new, unified system done, which is now hacked together with both of the legacy systems until we finally transition fully to the new system. The current plan is for next year, but the plan six months ago was for this year, and almost no progress has been made since then, so we're probably going to have two ticket trackers and two request systems for a while.

Actually, three ticket trackers and three request systems. The third ticket tracker is used to track work done on tickets that exist in the legacy tracker because the legacy tracker can't do that on its own, while the third request system is the oldest and most cumbersome legacy system of them all.

I was working on a bug in a legacy application and I was the first person to open the project in 10 years.. Found all the variables named with swears.. It was hilariously difficult to figure out what was happening lmao..

I've been working for the last 5 years on some large legacy code used in production, more than 100K LOC, poor comments (when existing) often outdated, huge parts of code that can no longer be reached, over-engineered class hierarchy, functions of thousands lines, huge parts of deprecated code that cannot be removed because "someone might still be using it". Statistically, every small change caused 3 new issues somewhere else and every bug fix or new feature required 10 times the time that would be necessary with a decent codebase. But after five years in hell I can finally say that... Oh wait, nothing changed, the code is still legacy and nobody is going to do anything about that.

The most C++ I know is from 5 weeks of 'learning' it in college. Now I've been handed a legacy C++ project from sometime before 2004 and am expected to figure out how it works, update it to either a newer C++ version, and compile it to NOT a 16 bit dll (like the current version is) to replace the one on our servers.

Ummmm... wish me luck

this is my legacy code, it's stupid, Change my mind.

a large number of lecturer and friends are against my thought. personally, i think this kind of code is told to be an OOP yet this is against the OOP concept. why ? first you assign the field to be private, but you implement Getter and Setter method later on, this is the same if you assign the field to be public in the first place.

another minor thing; yes this is old me, i use Bahasa Indonesia as a variable name.

working on a crappy legacy site written by an invalid. The job was to replicate an existing site for a school with the original's permission. I fix a shit ton of bugs and update the original.

For the first time ever I got a phone call from the original's owner to complain that I had fixed their site -.-

leave things broken from now on!

2 weeks in my new job. I started hating the work. I'm stuck working on legacy systems. This guys don't work on latest technologies.

Found this on a legacy app that is beeing migrated.

Just found a unit test in a legacy project that is over 300 lines long, creates files on the server and multiple records in the database, then deletes them all. It takes over two minutes to run.

Madness

236 lines of code in main doing like 400 things that should each be their own function DX
Fucking legacy projects
This is why I drink on the weekends

fuck oracle. fuck my company.

Using Oracle VM Manager/Servers to host Oracle Phone transfer solution without support coverage from Oracle.

Requiring Unix sysadmins to update to latest release and not telling that we do not have coverage from Oracle if anything goes wrong.

Gues what.. We've updated to Oracle VM Manager/Server 3.4.5 which was released this year and it uses fucking XEN hypervisor version 4.4.4 which has been deprecated and dead since who knows when. Latest release of XEN is 4.11. But that is not an issue, whatever, enterprise, legacy software, etc.

This fucking update introduced memory leak on the hypervisor which has been reported as per xen 4.4.4 history. Furthermore, we have no support from Oracle which means that I have to dig through mailing lists and limited information on the net since oracle has freakin support wall on nearly each of the major bugs found on that shitty software.

I have no idea whether any newer version of xen will work with that old Oracle Linux kernel or not.

Furthermore, Oracle provided great documentation on how to rollback the fcking update. Reinstall the hypervisor. Riiiight. XEN does not have export/import feature.

eh

Please who the fuck wrote sql query with 6 nested select queries as 1 giant view. Literally 6 paranteses. Garbage 30 year old legacy codebase Please fuck off i now understand why nobody wants to work on this bullshit

Working on a legacy app and couldn't find in the DB, fields for description, status, title, and assigned user.

I found them.

They were in the fields: User1, User2, User3, and User4.

How the hell does that happen?

Best: actually started to work on side projects, they are not just discarded ideas on the paper anymore, so excited about this one

Worst: legacy bolognese app nobody understands and doesn't have documentation coupled with weird API also without any documentation

"Well, I used Jekyll, but then switched to Hugo - but then that wasn't cool anymore so, I went with Nuxt, but switched to React, then Gatsby, then Next - and Now I just redid it in 11nty."

"So, did you ever write any blog posts? I thought it was a blog? The only thing you've done for the past 3 years is to update your basic website? That really could have just been HTML?"

(I'm not sure we can trust this guy to work on a legacy project...)

Contex: Working on a c++ frankenstein code (mixture of legacy and new stuff whith things depending on the client using it)

User Story: Migration from oracle to SQLite for half of the DB data

Summoner: One client wants to keep using legacy for now, therefore we need an strategy chooser templated singleton...

Satan 666 = Singletons + Static methods + Different compilation units

Result: 3/4 of the files of the full backend being modified for the migration.

Conclusion: When will be loaded on production company will probably lose many clients due to unspected bugs everywhere.

Insert potato here

I have a Yahoo app on my phone for some legacy purposes. I just allowed the storage access permissions when it was asking for it during the installation or something, cause like, who doesn't? I checked my Yahoo Mail on the browser tonight and saw copies of my mobile photos in it! It's through the Attach Icon > Insert animated GIF. WTF? So that's how you can easily get hacked from apps?

Asked to research angular 2 and do a POC on my own time, get assigned to a legacy product last updated in 2011, to watch all the new hires get put on the new tech.

Oh great...
I am slowly beginning to realize that my boss/manager doesn't care about refactoring at all. He cares about features and resolved tickets and thats why the code is a pile of spaghetti filled with hacks to fit every clients desires.
Also all of my coworkers work for themselves, ticket by ticket, either because they just don't care or because they are so frustrated that they don't care anymore. And here I am, an intern, and they expect me to cope with this deformed clutter of legacy designs, buried under hacks and workarounds, while implementing some new feature which in the end I have to put on top of everything else because nothing of that codebase can be reused. Fucking shit, fucking irresponsible managers who dont think about the quality of their product.

Working on modifying a legacy web project and just about every single element is `position: absolute` with crazy z-index juggling and hard-coded pixel sizes and positions everywhere 😭

To make it even worse, a bunch of the javascript will also change elements sizes and positions so it takes forever to track down why an element is where it is

One day, I have debugged some nasty legacy code and all of the sudden I wonder...

If Jesus walked on the water, can he swim on land?

My mentor always told me to tackle 1 problem at a time. “Go get the basic scenarios first then we can decide/derive what happens on complex scenarios.”

This shit helped me through my 4+ years in the company. Now that I’m a mentor myself I’ll make sure the legacy continues.

I'm bored af working on crappy php56 legacy apps written by short sighted programmers, makes my life miserable, but the pay is pretty good for a remote job which is pretty rare in here. Meanwhile I'm interested on exploring fundamental stuff on computer science and experimenting new techs.

I'm thinking about doing a PhD but too afraid if I can't finish it or the future opportunity isn't good enough since I live in 3rd world country in southeast asia. Also it probably takes ±8 years to finish it including the preparation.

I have no question, but it would be great if you have some advice.

5000 scss file with the name global.scss styling.

How fucking dumb can you be to fucking mess up a clean component based architecture like Foundation or Bootstrap and fill it with shit in a single file.

No wonder WP gets shit. The legacy code is usually shit.

And to put the shit cherry on top. This motherfucker had a settings.scss file with all general components and he never used it.

Fucker put different font size in px everywhere! Fucking asshole!!!

Company uses legacy "Web app" which only runs on an old version of Internet explorer. CTO told us to use a Windows VM since we have mac to run it. All for a website..... Ahhhh

My legacy is now indisputable in this company!

Utf-8 emojis for pipeline declarations will became a new era for pipes from now on.

The problem method calls into the...back-end framework!

The back-end framework was built on top of...the older framework!

The older framework was built around...the legacy framework!

The legacy framework was a...piece of shit!

And that's why the site just hangs!

Wasted 2 hours of my life trying to make an actionbar display white text on a dark background after migrating the legacy code from ActionBarSherlock to the supportactionbar.

And guess what? That fucking actionbar still displays black text.
What. The. Fuck.

Giving up on this for today...

We are so fucked up at our company:

While the support for our client hardware is running out, our operation departement has just found out that Windows 7 is no longer supported on new HW. Well, that for itself is not bad, but we have a really old tool for reporting our daily work. And because that mo*fu*ing piece of customized software still runs in 16bit mode, it will not run on Win 10 anymore.

Alternative solutions are too expensive, so I see that we will have to port that crap somehow from 1997 to 2017 ourself 😲 Replacing is not an option because there are a ton of Excel sheets connected to the database, even the company balance is made with that data (and also in Excel). At least it is our CEO which has built that crap. So he has to pay for his twenty year old sins!

After a rough exit from one company, I was diverted into Ops just to continue to have food on the table and keeping the lights on. This, over time, unfortunately made me more or less unemployable as a dev again. Got stuck in that place 13 years doing almost no professional coding.

During the last 5 years I took courses, got side jobs writing articles and tutorials, went to interviews and generally worked hard to get the fuck out of ops and into development again.

After getting to choose between level 1 customer support and quitting in a re-org, I quit without having a new gig. I got a lucky break through someone I'd worked with earlier to start a junior position working on some legacy systems with legacy tech.

After all that work late nights churning away using up my passion for coding, I now can't make my self pick up even Advent of code or Hacktoberfest... My passion is dead... I hope I get it back, but for now I fill my spare time with my guitar...

team lead/senior telling you that you're probably going to break prod and have to patch it for the next couple of weeks when working on one of the first migration epics on legacy monolith, but we'll get good data from it doesn't make it any less terrifying

We have a bunch of legacy applications that runs on Windows only. I'm pretty much the only dev here who doesn't use a Windows machine.

In order to run those applications, I need use remote desktop to a Windows VM.

I use a Mac. And I use a lot of keyboard shortcuts. Case in point, CMD + L to go to the address bar in the browser.

This happens every time when I need to access those applications.

me: *remote desktop to the VM
me: "oh I need to get to the index/landing page"
me: *CMD + L
VM: "I'm locked now"

It is fascinating to see how my motivation and productivity decreases while working on legacy code.

Ugggh. Has anyone else on here worked with MFC?

I've been updating some legacy software and it's been like wading through a swap that was caused by a malfunctioning trailer park septic system: no map, and mostly shit with the occasional nasty surprise.

It drives me Insane that AWS still doesn't support Swift 3 for iOS. We're almost to the point where Apple is going to drop Swift 2 support in XCode and Amazon STILL has not gotten it.

I've started deploying Gateway APIs in Objective-C and linking them to the bridging header just so we can finally move foreword in our company and quit relying on legacy Swift support. Which is something I was really trying to avoid because we don't like mixing languages unless absolutely necessary. It's not a problem, but it's incredibly annoying to me. What IS a problem is having to start new projects already using legacy code from the very beginning.

What is amazon going to do when the next release of XCode comes out? Tell all new customers to downgrade?

Why even offer native Swift APIs if you're going to go this long and still not migrate, Amazon?!

Still trying to understand a good old pile of legacy:

function isValidDate($value) {
if ($value == "" || ($value == 0 && is_numeric($value)) {
return true;
}
// goes on to check if value is some number between 2000 and current year
}

@Gilles had a similar rant and reminded me of a story...

As a kid I learned QBasic. Moved to VB5 and later VB6. Because of this 'knowledge', I was the one who had to maintain legacy applications at my previous job. All of those applications were in use at various banks. On first work day in 2011 all hell broke loose - no date input control would accept the date anymore. I quickly discovered that the max year on date inputs was set to 2010. Later, I was told that nobody expected these applications would still be used in 2010 so they entered it as a distant future number. The funny part was that one bank was still running apps written in VB3 and I had to go back to basics. Didn't even know how to edit basic controls in that interface :D

Good times :)

Notifications are not being sent from github to slack. Ok. Looks like that legacy slack github integration that has been telling us its no longer supported for months has finally been deactivated.

Fine. I'll cave and upgrade all 45 of our repos to the new integration.

Thousands of clicks later, finally done.

*but wait*

"Notifications still don't work?"

That's when I saw this notice on github.

FML I want my hour back.

My second worst experience with legacy code:

JSP with inline java to create JavaScript which creates HTML on every fucking page load.

Luckily I leave that company too.

Let's face it: I am and will always be a tinkerer. Yes, I know my ways around, I can sneak into legacy code bases easily and throw new stuff in there, I've seen software stacks. But scarcely sound design, really modular. Even from the cleverer, experienced ones. They can master more complexity, so they can handle more spaghetti. Some essay from the 80's had this grand idea to organically 'grow' software. That's how it looks like most of the times: cancerous, parasitic super fungi (armillaria). Yeah, we all know have to fight bit-rot and entropy, but it was all lost before already. We'll never get rid of legacy protocols, legacy code.
And even when we go green field, start a fresh. Yeah, take a great design, make everything new, after some months of throwing features and outer constraints at the thing, it's the same old mud again.
But we can still dream on: some day I will design great APIs, I will have great test coverage, documentation, UML design, autometed tests, fuzzing, memchecking, I'll work professionally, clean coder style.
Pfft forget it. Maybe change for consulting, because we'll continue to dream of the 'clean' code, so you can sell the next 'recipe', development method. It's like diets. As effective. For the one selling.

I love working on legacy products. You just need a good shower and possibly a therapist after.

- Sensitive data sent over the internet encrypted with DES (not even 3DES). Guess it doesn't matter that the key (singular, for the last decade) is basically 0123456789ABCDEF.

- Client databases with open default port, admin/admin superuser.

- Critical applications (potential for substantial property damage, maybe loss of life) with a single point of failure and without backup.

Suggestions, to slow down a bit with sales, so we have time to rewrite this steaming pile of crap are met with the excuse: be more pragmatist, this is standard industry practice.

Some of this shit can be fixed on my own time if my conscience nags too much, but others would require significant investment of time from multiple developers, which would slow down new business.

Guess the pay is ok, so that's something...

Got rejected from a really nice opportunity today. Irrelevant experience as it seems to the company.

As it turns out I'm an unlucky beginner in the industry who's stuck with a wrong, legacy code project. Doesn't mean I don't know anything and I can't learn new stuff. They were not judging capabilities, just judging people by the project they're working on in their current firm.

God, the dude who "assisted" me today can go and fuck himself with a cactus.

I need to configurate and integrate some cms into a project. But since the documentation is utter horse shit and superficial, it's fucking torture to do so!

So after creating an issue on their helpdesk, i get an answer from some employee there. Instead of actually posting something useful, he decide that he could instead quote the fucking documentation.

Of course, he also quotes the very page i mentioned in my issue for being COMPLETELY USELESS. This goes back and forth. And he keeps just quoting the fucking documentation.

So i decompiled their product and painstakingly worked out how the feature worked that i needed.

Fuck you support asshole. I hope you get to maintain a legacy VBA project!

My exact reaction when ,I was researching on legacy programming language and their copyrights for my intellectual property rights subject.

Found that
Python was released before Java did.
But the popularity Java claimed was faster than python

Python first release date 20 Feb 1991
Java first release date 23 Jan 1996

Could anyone explain y python gained is momentum later!?

By Thor (not the god, the dragon), Belial and Thor (the god, this time)...

Just got the sources for the software that runs on the SDR for my project. I think I just found the mother of all legacy code:
The whole behaviour is described in a single, 4000 lines C file. Most of the code is in a giant switch with cases selected from an enumeration with names that don't match their function. All varnames are overly long, yet hopelessly unhelpful. And why three fuck would you use pointer[0].data instead of (*pointer).data or pointer->data like a sane person would !? pointer isn't even an array, so why would you use []?

Today I've landed on a legacy project which still uses mail() method in PHP. Just gonna enjoy this one.

Hello and welcome come to hell for developers. Take a seat at any open computer.
You may have noticed we did away with the fire and brimstone.
Instead we just have you maintain the legacy code from your first job.
It's genrally html, php, javascript, and css all on the same page and all mixed together.
We would say have fun, but that's not really the point.

Why the f*cking hell would you put the new guy on the legacy cleanup project???

I'm faszinated by some dev's ability to write legacy code.
Not maintaining but plainly creating code so horrible, that it can be considered legacy.

I wrote a new API for a silly Application because the old one had hardly anything to do with rest. At all. And despite the code being only 2 years old, it was still unmaintainable.

Now that I'm finish with this task, i got the next generation of the angular Frontend.
A guy wrote a completely new version of the frontend in angular5.
Only untyped variables, no documentation, no tests at all, no idea whats going on where,....

I thought my job was to adjust a few URL's and change some DTO's, but now i have to refactor everything again...
And the pain continues.....

Agreeing to work on supporting someone else's legacy code instead of insisting on razing it and rebuilding.

My lovely team and I inherited a legacy app written in Angular 14.
We love it when we get fucked by Pajeets like this.

We love tons of `any`-s in the codebase.
We love unreadable code with 5 levels of nested ternary operators.
We love the lack of a README on how to actually build/start the app.
We love the outdated dependencies.
And we absolutely love it when you use a paid package that costs $1755.

Has anyone ever had the joy of dragging their employer kicking and screaming into the 20th century?

I've been here a little over a year, and slowly but surely I'm moving us forward.

We implemented git via GitLab (our it department already had an on premise installation), I've got us up and running with basic pipelines, I'm pushing TDD, im leading the move towards APIs for new development, and I'm implementing new projects to streamline our work, mainly by automating tasks which currently can take hours with hundreds of manual changes.

It's slow going, and there's lots of legacy business critical apps which we won't be able to change, but we're getting there.

If things keep going smoothly then I might even ask for a ride to reflect my benefit to the business, and extra responsibilities I've taken on which are far beyond my official job as an SQL Developer

A "portal" built on Drupal 7. Started by someone who cannot do anything outside Drupal, and overseen by someone who believes JS to be "low level programming" (he literally said that).

What normally would be a table with 7 columns is instead 7 tables joined together. That goes for each data structure.

Each page, built in a separate module, either manually includes the same css files, or simply copy/pastes them.

Old, legacy modules have been hacked, and now depend on newer modules... Which, in turn, depend on the same old ones.

The theme contains huge, hardcoded parts of logic, so it can never be updated.

Worst part of it? It's only 3 years old. And there are people buying it as SaS. Already hitting bottlenecks at 2k users.

Windows containers with Kubernetes on AWS and Azure are thing now.

What does that mean? Is it now possible to containerize system critical windows 3.1 legacy software from the 90ties (like the ticketing software at Airport Paris Orly) and orchestrate it in the cloud?

Do you know any use cases for Microsoft Windows in the cloud?

I think the worst time was when I worked on a work project through the night. It was at my previous employer, I was forced to work on legacy php projects I knew nothing about. Nobody could help me and I was always doing days over tickets which were just a pain in the ass in an old magic framework and a custom build cms :c.

I couldn't motivate myself for days and eventually when the deadline came I worked through the night and committed in the morning, then I jumped into bed. I realized that this was a big sign that I really had to quit, and switched companies several months later.

Ooh what a nice feeling it is when you come back from a short vacation and everything is in the gutter... My team is divided into the two other teams... (I said divided but I ment everyone got assigned into team X... And I am the only one who was put into team Y)

Besides the whole team fiasco, I think my legacy project decided to role around in the garbage... Because I have no idea where all those bugs came from...

One positive thing is that I won't be working alone on that legacy project anymore, at the start of next week I get help from my new team... Now let's hope they don't suck!

My best mentor was at my first job at IBM. The senior dev took 2 weeks to pair program with me and get me up to speed on all the applications, tips and tricks, and the different legacy codebases. I learned more in those 2 weeks than my entire 4 years at college lol.

Ubuntu 17.10...

WORST UBUNTU RELEASE TO DATE!

Why oh why did they go with /swapfile by default? I was legacy booting with UEFI enabled and it still didn't work! And don't get me started on nouveau (Nvidia OSS).

When I click "use proprietary software" I want the OS to do everything in its power to just work. Disable 3D acceleration if you must - at least boot to a console.

I'm scared to try it on my main desktop now!

I switched to Linux Mint and I'm happy now, I just needed an instant OS that works. 😊

Working on a big project with lots of legacy code and terrible code. Full of jewels like this:

$('.form-item-to input').parent().removeClass('isOpen');

Man... .form-item-to IS the immediate, direct and only parent of the only input child!!!

You know your day is gonna be bad when it's Monday and you are told to work on a badly written legacy flash application!

I've worked on a year to replace an old legacy system after years of shitty maintenance. We're almost there. So damn fucking close.

Product Owner: Hey, can you guys own this incredibly fragile legacy app built with Grails, Angular and Mongo?

Me: No

PO: Go on. You can rebuild it!

Me: Sigh.. ok

- 6 months later -

Me: When can we rebuild this bloody app??

PO: lol sry no budget lmao!

Current status: Writing a markdown document containing all my tips and tricks for fixing bugs in our apps so we can handover to maintenance. Including files I commonly have to look in, handy keyboard shortcuts, IDE settings and other tools that have made debugging easier. I figure if these guys are having a bunch of legacy apps dumped on them when they have no iOS experience, I should help them out as much as I can before I move projects.

Where and How do you make developer friends.

My coworkers are smart and decent developers but they learned on the job for the job.

But they're not interested in discussing improvements to legacy projects that barely still work until they break and we need to rush to recreate them 'better'.
or sit on a call on the weekend working on spontaneous personal projects that usually die cause another idea came along.

Sometimes I really just want someone I can hop on a discord call with so they can criticize my projects and brainstorm ideas and improvements with me

Writing unit tests on a weekend and catching up on work that needs to be done because I m too busy on weekdays to have time to think about this...

The sad thing is test coverage is shit in the entire code base as boss just decided to start enforcing requirements now... And I have this huge migrating from legacy system project that needs to be merged. And we'll the legacy system is even shittier

So I have to write unit tests for shit code that was never written with testing in mind...

On the other hand I reworked some testing utilities to make it easier... For everyone... I want a huge bonus.... That I probably won't get...

Is it reeeeaaaallllyyy that fuckin hard to use just one js framework on one page?!

Yeah, I know project has several included (for legacy reasons) but that doesn't mean it's ok to mash em all up together on one fuckin page!!!! WTF!? Or at least implement it correctly ffs!! Pissed af!!

Hogwarts legacy is out, and here I am, on a nice free Saturday, walking 6 fucking miles to a fucking mall to spend the fucking afternoon in fucking clothing shops.

Fucking *kill* me.

Last week me and my friend have been changed from a legacy PHP project to new Ruby on Rails-based setup. What, in first instance, looked like a great improvement, now becomes a nightmare.

All this convention-over-configuration is awesome - but only if you already know the conventions, or if somebody told'em to you.

And everything is going even more out of control because the damn project is based upon Spree gem and several other extensions, that MUST be changed to meet out company needs.

I'm getting really mad with all this pressure. Ruby seems to be a great language, but I'd rather be working with Laravel. Its overall organization, the centralization of CLI commands in artisan, and the astoundingly clear, eloquent, direct and well-designed documentation made my adoption curve there a little more pleasant.

I mean, legacy PHP systems are awful, but Laravel framework sounds way more easy-to-learn and well-constructed when compared to rails.

But given all this nightmare, I really want to be proved the opposite.

"hey the hi-8 camcorder's working again, can you get this PCI tv tuner card working so we can transfer the tapes to a digital format"

here we go again...

no stickers, so throw it in a machine, boot debian's installer, switch TTYs, "lspci": okay, a pair of "Brooktree BT878" devices. Drivers? ..."support built into most kernels since 2.4." Didn't they remove a lot of legacy hardware support from 5.x or 4.2x or so? Debian works with it... oh, "Debian Sarge." Kernel 2.6. FUCK... well, we'll try Debian 10.6 latest and see what happens.

Currently installing Debian 10.6 on a victim machine from a nonfree ISO to test this. (goddamn, how many times have I installed debian onto something?) Hopefully I don't have to go find a Debian oldoldstable ISO or anything...

Best:
- I built a good automation mechanism with a decent UI [slackbot]
- used as few frameworks and ext libs as I could. Mostly based on bare java
- client wanted to migrate it to Spring
- got 3 peeps assigned for the migration
- 2 months later their effort failed.
- win: my project has not been molested with Spring

Worst:
- i had an idea to develop smth on top of jmeter, using jmeter as a lib
- I downloaded and imported jmeter's src code
- static contexts, singletons, jmx/rmi everywhere [java is deprecating rmi support]
- not gonna happen... Not gonna build a new project on top of a legacy codebase.

I was typing a rant about this deadlines of a legacy project I have to work on but I'm just too tired/stressed/angry todo so... Maybe in a week or two when the fucker is finally done...

Just started a new job as a software developer, even though I basically applied as an embedded software developer. I knew from the interview there was gonna be alot of legacy / high level stuff and they were pushing me away from embedded with the promise I could do it 'later on'.

Finally started and it turns out there's a shit tonne of legacy Python code for their non-existent test framework that's basically tied directly into a Qt GUI app and I'm doing shit that nobody else wants to do. Can't see myself wanting to do this for anywhere more than 2-3 months. Should I just bail now? Seems a bit dodgy if I leave having only worked there for a week? Job actually pays really well though.

Plan was to take an extended vacation around July/August, so quitting this early and then telling another employer later on that I need to bail for summer seems wrong also, not to mention COVID sucks and is making everything hell now.

I hate servers that only support EFI boot with a passion. Yes, legacy / BIOS boot is old, but it was so simple. I've been spending hours trying to get EFI boot working on servers with swraid-ed disks and *nothing* works without ugly hackish patches all over!

Anyone successfully got an EFI partition (/boot/efi) on an MDRaid device? D':

Hey, sysadmins / legacy devs.

What is the cheapest way to get my hands on unices' shells? AIX 5.3/6.1/7.1, SunOS 5.x, HP-UX 11.*,..

Needed for playing around.

a question for y'all:

just out of interest I would like to know:

are you *mainly* working on legacy stuff that is - without a question - just too old? everyone in your corp knows it needs rework but "EfFoRt JuSt ToO hiGh"? Where at the same time, most of dev time goes into maintenance and bug fixes instead of feature implementation.

If yes, do you fear that you're losing relevance on the market by not keeping up to date? What are your feelings about that situation?

did you maybe even quit a job in the past because of such situations?

---

Why do I want to know that?
- Had some beer
- As a freelance dude I often see battlefields right out of hell. I csn easily go, but the dudes working 9 to 5 on that??? Hoe can you oO

Managing a small team - poorly.
I was in charge of testing a legacy calculations engine together with two scientists, for whom I set up a python and interop environment so they could test the engine easily.

The two were very excited at the thought of validating the calculations and in fact found many bugs.

I was very supportive, told them to fix the bugs and gave them a pet on the back.

All three of us were happy the legacy engine is shaping up, that's until my boss heard of it, and boy did he grill me hard for it.

Turns out our efforts were highly unappreciated by the client, whose only request was that we test the engine and report the bugs. Not to fix them. My goodwill cost the company a lot of money, since the client paid by the hour, and was now due a refund. Crap.

It took me a year to finally understood the moral of the story. Which is to always respect the client's wishes and convey maximum transparency to him.

So I started my current job 7 months ago

I like the company and feel like I fit in with the people. The work though....

So the project I'm on has an Apache Wicket front end.... Pretty sure this thing was written around the same time I was learning to wipe my own ass. The senior dev is unreliable af and even when he is here, he sounds like a dial up connection.

Today is my last day with this turd. He's leaving at the end of the month and I'm on leave the coming week. So I'll be coming back to having this project basically to myself... Mixed feelings... One the one hand, I'm glad to be rid of this guy... On the other, this is a legacy project and I still don't know the half of it

I'm currently working on a new (for me) legacy database that store percentile numbers in a varchar column . Seriously who the fuck had the that brilliant idea!!!

Meh. FFS. Thats how this shit starts.

Get a call to say 2018 Bank Holidays not showing on legacy web calendar.

/me looks for bank holiday code in PHP file ..... no dice.

/me finds a dBase table that holds all Bank Holiday info. Not ideal, but I can work with that.

Enter all Bank Holidaya into dBase. Sit back, relax, wait for page to reload to show me Banks .... no dice.

Huh??

Read code more closely ......

Included file (inline, half way through PROCEDURAL FILE FFS) and notice that the linked file has all Banks hand formatted into Calendar events, and minified.

If I ever meet the old dev in the street, so help me god. 🤬

Don't you just love it when there is no formal spec. you get a few mspaint slides and told a delivery date, scope and slides are changed by management weekly, not necessarily informing you of it. Then when your failing, deadlines pass you by you still have no clear spec 2 weeks before release, partial backend because core business devs are busy doing support on the legacy systems. No frontend cause it's been changed, redesigned and you've been forced to change frameworks and technology so many times due to corporate policy and legacy systems with another dev group holding your balls with what they allow you to do and use. Id complain but at least we've been told to be agile. This is my life now, we lost all hope and stopped caring. And management wonders why the deadlines and estimates are all off.

Oh my... Downloading dependencies on the hospital's network is a sloooowwww draaaagg. It's almost like hospitals aren't suitable for developers!

Joke aside, I'm enjoying my orange while waiting for that download to finish and it occurred to me - an orange - a food that very strongly associates with a hospital in our country! And a mandarine is a fruit that means "Christmas!!!" I believe that's a legacy in post-soviet countries :)

And here's my question. Do you, folks in other countries, also have any foods (preferably something rather ordinary) that have strong similar associations? Not necessarily Christmas or hospitals though :)

(I can guess rutee's association :) )

We received legacy project for support and fixing.. it had few issues:
1. There was a controller called MainController. This guy was the soul of the project 10k+ lines, heavily dependent on the data from the database.
2. We didnt get the data. Just the database structure (we couldnt run the app at all)
3. At the very end of that controller there was a "simple" eval($_SESSION['somevariable'])
4. We had no documentation and had to guess how it works...

Someone really had fun screwing up this project. Needless to say we got rid of it quickly. :)

When you spend weeks working on a new codebase in Python and you have to jump into the legacy PHP one to fix something nasty

Patching a legacy project: all logic inside an 8000-line file called class.cms.php, on frontend, one js file with about the same file size...

Since when has Brave based on the Chromium base been the main download?

Today my legacy Brave based on their own base crashed and as it seemed unrecoverable, I tried reinstalling. But now I'm stuck with this crappy Chromium based browser... I hate the non tab-pages and lack of tab peeking.

I initially had the Dev channel version but only as a backup for my main Brave because I realized how crappy it was, safe in knowing that at the time the main download was the old Brave Core. Now I'm really annoyed.

13.5 million steps on my little Fitbit Zip named Dino. Long walk last weekend and lost him. Backtracked a mile and found him. So happy. But car had run him over and crushed Dino. So sad.
Carefully operated on him and although his screen (face) was smashed he had one more synch (breath) in him with me holding his little metal prongs.
Gave him a little funeral. He will forever have a cherished spot in my sock drawer.

I went to the Fitbit store and Sally his little sister was born to carry on his legacy.

Best : Open source projects.
Worst : Legacy proprietary systems. Most of them you can only wish you have documentation and lucky if you are able to run those systems on your computer.

I have found a DVD with a Windows XP backup file with my late mother's photos on it. However, nothing seems to open the file. I, of course, did a lot of Google searches on how to do this and what it seems to come down to is a need to run the restore on an XP, Windows 7, or Server 2008 machine. There are several legacy ntbackup restore programs out there, and Microsoft seems to still have a page for downloading that, but it relies on the long-deprecated Removable Storage Service that no longer exists on Windows 10. So, a) Microsoft are a bunch of jerks for not supporting restores of legacy backups and b) does anyone have a successful method you've used to get a BKF file to restore? All the things I've tried say the BKF file is corrupted, but how to know for sure when Removable Storage Service isn't present?

Since the issue is within the legacy backend data, this brings us the great opportunity to solve and sanitize the data on the frontend and therefore killing the performance of the application! Sincerely, a manager that doesn't give a shit

Helping to fix legacy code on a staging server. No version control (at least not that I am aware of). Besides rare code comments, no way to see the author, time, or even purpose of customizations that have been made. No fun!

Trying to port a legacy Firefox add-on I didn't write to WebExtension. Failing so amazingly...

Vague explanations, no tutorials. Mdn has a nice documentation but no tutorials. What's up with that??

Also, JavaScript. And stuff I didn't write. Just perfect. 😑😑😑