This is not a joke. This is not something I wrote to be funny. This is not found randomly off the internet. This is a real part of the project I inherited: a function that not only is more cumbersome to use than the simple <Array>.contains that it wraps, but rather than returning the boolean result from the function, sends it through an if statement and returns hardcoded true and false values for... Good luck? I guess?

Conversations I've genuinely had at work:

Me: "Do you want some advice understanding that function?"
Dev: "Yeah, please!"
Me: "Get a plastic bag and some super glue..."

Dev: "I think I'm seeing the light at the end of the tunnel!"
Me: "It's just the train of mental bitchslaps coming in the other direction."
... Some time later
Dev:"You were right... "

Dev: "If the system is so unstable, how does it keep working?"
Me: "Do you see any goats in the office?"
Dev: "Uhm no... Why would there be goats?"
Me: "There aren't, now, we ran out."
Dev: "The hell are you talking about?"
Me: "We just sacrifice our own blood to Cthulhu these days, it's cleaner and we didn't have to pay to have all the goats blood and waste matter to be cleaned up. That and it was needlessly cruel to the poor goats and that is why there is no goats and despite conventional logic the app continues to work."

Dev: "So what language is the web app written in?"
Me: "You need to understand I inherited this project, I had nothing to do with it's spawning..."
Dev: "OK, that sounds ominous... How bad is it?"
Me: "Java..."
Dev: "..."

Dev: "So what's it like working on this project? What should I expect?"
Me: "You'll call your grandmother during your lunch break just to know there's a world beyond this project. You'll go home, nose bleeding and you are gonna sit in the shower and rock back and forth, holding yourself and feeling like you're suffering imposter syndrome. You'll question why you joined this team and it'll get inside your head til it's all you think about..."
Dev: "Damn man, why are you still on it?"
Me: "Stockholm syndrome, it's too late for me..."

PM: "You're such a dark person, we're not gonna find you hanging from the lights one day are we?"
Me: "Impossible, we use those industrial fluorescent strip lights, there's no cord to hang from."
PM: "That really wasn't the comforting answer I was looking for."

Head of department: "So I need to apologize, you were never meant to be left on your to manage the product on your own, it's something someone way more senior should have been doing and we reassigned him. It wasn't professional of us, it wasn't fair of us, we're sorry. Truth be told,we're impressed you've not gone mad."
Me: "I think I have. Wibble."

A card goes round work for a sick member of staff I've never met.
Me: "How would you describe her condition?"
Dev: "She said that she 'survived' the surgery."
Me: "Yeah, I'm not great at being appropriate but even I think writing 'glad to hear that you are not dead' in a get well soon card isn't the done thing."

Not a rant about anything in particular. Just a summary of some feelings stored in the hateful part of my heart.

Developing for Android: Add this third-party library to your Gradle build. Use (this) built-in Android class to make the thing work.

*Clicks link

Deprecated since API version SUCKMYDICK-7. Use (this) instead

*Clicks link

Deprecated since API version LICKMYBALLS-32. Use...

Developing for Windows: Please use (this) API call. It was literally already available before Bill Gates was born. Carbon dating has placed this item to older than the universe itself and it is likely the entry point for the big bang. It is also still the best way to accomplish (task).

Developing for Linux: "Hmm, I wonder how to use this"

> > > Some shitty mailing list in small blue monospace font tells you to reference a man page that is three versions behind but the only version available.

What? Those three sentences didn't explain it enough? Well, maybe you aren't cut out for this type of thing.

JavaScript: you know how it is.

SQL: You expect a decent-quality answer from stack overflow but you always get an outdated and hacky response and it's using syntax from Microsoft SQL. You need MySQL.

C#: A surprising number of Microsoft forum results ranking high on Google. You click on one in hopes that it will be of any sort of quality. You quickly close the tab and wonder why you ever even had hope.

Literally any REST API: Is it "query" or "q"? "UserID" or "user_id"? Oh, fuck, where's the docs again?

You thought you escaped JavaScript, but it was a trick!: Some bullshit library you downloaded to make your other library work redefined one of the global variables in the project you inherited. Now you get 347 "<x> is not a function" errors in your console. Good luck, asshole.

FontAwesome/ Material fonts/ Any icon font pack: You search "Close" for a close button icon. No results. You search "Simplified railroad crossing sign without the railroad". You get a close icon.

I think that's all of my pent up rage. Each of them were too small for an individual rant so I had to do this essay.

Here's a conversation I had at work:

Me: "this project that I've inherited, aside from the UI problems it has, it also has severe code problems that need to be fixed"

Project Manager: "I don't care about the code. The code is not my concern. Don't waste time on it and just make the app look good."

Inherited project from another company that the owner wants updated rather than rebuilt.

The comments could write a programmers joke book as you can tell it's been passed between multiple developers.

This is a literal excerpt
//Not sure why this line needs to be here but it breaks without it
//Nope I don't know either
//FFS now I have to deal with this. Thanks guys :/

Trying to use stack overflow driven development (SODD) on my inherited 10 year old php project

I have this project I've inherited, yea I seem to do that a lot, but this damn thing, has to run in php5.4, has deprecated functions for php7 everywhere and a lot of them and there's no classes anywhere beyond some libraries.

Everything is procedural with random scripts being injected left right and center.

I kid you not,

$thisThing = true;
If(x==y)
require "path/to/some/script.php";
else
require "path/to/a/slightly/different/script.php";

If($thisThing === false){
// well it was modified in that small block about 10 different times
}

Those injected scripts then accept data from the parent scope so, looking at file X, you need to have open file A,B, E, and M to understand where variables have been initialised and what there current state could potentially be.

Basically this thing was bandaid after bandaid for feature requests with 0 refactoring.

Here I am trying to implement some basic functionality (should only take an hour or so + a bit of manual testing) but no, I'm literally at the point of hitting the delete button on the entire project and starting again.

A couple of months ago, the father of a friend of mine, asked me if I wanted to help him out with a project.

His late father, whom he inherited a one-person upholstering company from, once created a system in filemaker to do, among others, his financial administration. This system, however, grew organically as time went by, but he passed away before he explained to his son how it worked.

Now this man was running the company, using the parts of the system that he knows, but things were starting to break down. He asked me if I could help him understand what is going on and fix a couple of things.

However, the more I look at it, the more I realize what a monstrosity this has become, because the system has never been cleaned up. For example:

- There is a suppliers table, with the columns "E-MAIL" and "EMAIL". The latter one containing the supplier's website address.
- In order to be able to generate year reports, at the start of a year he copies the previous year's file, removes all records from it and starts using that as the new year's file. (This year, he accidentally created a shortcut instead of copying...)
- Some tables have a misterious column called "#1". It always contains a 1.
- The system consists of about 20 files, each of them containing a single table, although only 10 of them are really used. The other ones are just legacy.
- File, table, column, and layout names are capitalized randomly (all caps, no cap, starting uppercase) and are usually abbreviations, like "st2", "oms3", "off\rek", "b", "VERDBEST6" and "antst".
- One table has 92 columns.
- Of those 92 columns, only about 20, maybe 30, are in use.

Now, my task is finding out what parts are useful and in use, extracting those and create a baby monster out of the giant monster this system has become.

Sidenote: I actually enjoy having to learn a bit about accounting in order to understand this. Planning to use the knowledge I gain to keep track of my own finances.

Just inherited a project from a "senior" with the variable names 'gggg' and 'ssss' in it...

This is the first time I have inherited a project. ever. I have always seen people on devrat ranting about inherited projects. Never had I experienced it.

Now, the design agency that hired me would outsource web projects to developers before hiring me. I was recommended to them.

Now then. Today I was tasked to fix a couple of issues a previous outsourced developer had abandoned. I had a look at the issues and started fixing them one after the other. Its a wordpress project. Coding for wordpress is super fucking easy by the way.

You create a default page by going to the admin dashboard.

You can create a custom page by creating a page-PageName.php file. and place all the bullshit you have for the custom page IN THAT FILE.

So this developer who i assumed claimed to be a professional. PASTED ALL THE FUCKING HTML IN THE WYSIWYG TEXTBOX. WHO THE FUCK EVEN DOES THAT?

THIS WAS A FUCKING SIMPLE TASK. THIS ASSHOLE CREATED A CUSTOM PAGE CALLED HOMEPAGE AND PASTED THE HTML IN THE TEXTBOX. WHY THE FUCK?! ARE YOU FUCKING CRAZY DUDE? AND OH MY GOD DO YOU NOT KNOW HOW TO WRITE HTML WHAT THE FUCK IS ALL THAT &QUOT CRAP. YOU MY FUCKING FRIEND IS THE FUCKING REASON THIS PLATFORM EXISTS. BE PROUD. YOU MADE A DIFFERENCE. YOU CAUSED A PLATFORM TO BE CREATED.

PLEASE DO ME A FAVOR AND NEVER FUCKING TOUCH A COMPUTER EVER AGAIN! YOU ARE NOT WORTH IT.

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!

When you inherited that legacy project at work...

It's fucking never worth it, to be decent to colleagues. I got prove of that just this evening. Sorry, this rant will be a bit longer.

A colleague of mine inherited some legacy project that I worked on in the past. He clearly hates working on it. And tbh. I can't blame him for it. It's not very fun. He also makes virtually no effort to become more proficient in it.

This usually leads to him calling for my aid, whenever any problem arises, that would require any kind of effort to solve. I would normally cave in and help him. Mostly due to the fact, that without any intervention from me, it would end on my desk sooner or later.

That changed in the last few months, as I simply couldn't make free time to help him. anymore. I was working overtime and the associated project barely got done on time. During that time I would, as politely as possible, deny him. He knows fully how stressful the project was getting.

Today he asked for help again. I denied again, as a task was due very soon. He didn't reply to my message afterwards. After a few hours suddenly I got a bunch of his jira issues assigned to me.

The motherfucker simply shoved _all_ of his support issues to me. Not only that, he also assigned the issue he was asking for help for earlier as well. All without consulting me or anything. Then he pissed of into his vacation.

Some of his support issues have been created last year! And they are still not solved. He simply isn't replying to questions in those issues or just assigns them to others colleagues without any instructions.

Fuck him. Other colleagues don't even respond to him anymore. He fully fucking knows that I have a tight deathline on my current task. And still he chose to dump all his work on me, so that I have to waste time to reassign it and report it to our superior.

Fuck him for creating more stress in this already stressful situation. Enjoy your vacation you fucking leech. I will have quite a "nice suprise" waiting for you, when you return.

At one of my previous gigs, the IT director was just some guy that dated the bosses daughter. When she inherited the company he went from entry level data analyst to his new director position. IF he decided to show up to work at all it would be at just in time for lunch, and then he'd head out shortly after.
This guy would ask for an estimate on development and then start the timer when marketing started working on the project. This would often lead to us estimating something like 4 months on a project, and then waiting on marketing for 3 of those months, leaving us with 30 days left.

I would describe the test project i inherited as a watermelon test suite,

Green on the outside..............................

Red on the inside

I once inherited a project that had been outsourced for more than 6 months to a company at the other end of the world. Although the PM had almost daily contact with the developer, the project wasn't technically followed up.

I had already recommended code reviews 3 months before I inherited the project. But of course these had never happened.

The project contained all the nice-to-have features, but the core wasn't working. Loading the home page (with 20 records from a DB) took 15 minutes.

We then had roughly a month the get the project straight.

So we had this legacy Objective-C codebase for a mobile app that was actually pretty good: I'd inherited the codebase and spent the past several years gradually improving it and I was actually quite proud of the work I put into it. So of course management decides to scrap it (with NO consultation from the engineers) and outsource a complete rewrite of the app in C# for Windows Universal.

Let me tell you. That code was without a doubt and without exaggeration the *worst* code I've seen in my close to 30 years of experience as a developer. I mean they broke every rule in the book, I'm talking rookie mistakes. Copypasta everywhere, no consistent separation of concerns, and yet way too many layers. Unnecessary layers. Layers for the sake of layers. There was en entire abstraction layer complete with a replicated version of every single data class *just* to map properties in pascal case to the same property in camel case. Adding a new field to a payload in the API amounted to hours of work and about eight different files that needed to be modified. It was a complete nightmare. This was supposed to be a thin client, yet it had a complete client-side Sqlite database with its own custom schema (oh and of course a layer for that!) completely unrelated to the serverside schema, just for kicks. The project was broken up into about eight or nine different subprojects, each having their own specific dependencies on various of the other subprojects in such a tightly-knit way that it made gradual refactoring almost impossible. This architecture was so impressively bad, it was actually self-preserving!

Suffice it to say it was a complete nightmare, and was one of the main reasons I ended up leaving that company. So just sayin', legacy code isn't always bad. :)

The billing system on an enterprise project that I've inherited is a nightmare. The client complained that an aged receivable was being reported as 31-60 days overdue when it should be 0-30 days overdue. I checked the system, and discovered that an account had multiple invoices. One was due in May and one was due in July. The system took a large payment, fully paid the invoice due in July, and partially paid the invoice due in May. That seems wrong.

I checked the code and confirmed my suspicion. The system is ordering open invoices by their creation date, not their due date. The invoice due in May was created after the first invoice, but had a much smaller window to pay. I'll bet anything the original coder assumed all invoices would have the same window to pay.

I really need to vent. Devrant to the rescue! This is about being undervalued and mind-numbingly stupid tasks.

The story starts about a year ago. We inherited a project from another company. For some months it was "my" project. As our company was small, most projects had a "team" of one person. And while I missed having teammates - I love bouncing ideas around and doing and receiving code reviews! - all was good. Good project, good work, good customer. I'm not a junior anymore, I was managing just fine.
After those months the company hired a new senior software engineer, I guess in his forties. Nice and knowledgeable guy. Boss put him on "my" project and declared him the lead dev. Because seniority and because I was moved to a different project soon afterwards. Stupid office politics, I was actually a bad fit there, but details don't matter. What matters is I finally returned after about 3/4 of a year.

Only to find senior guy calling all the shots. Sure, I was gone, but still... Call with the customer? He does it. Discussion with our boss? Only him. Architecture, design, requirements engineering, any sort of intellectually challenging tasks? He doesn't even ask if we might share the work. We discuss *nothing* and while he agreed to code reviews, we're doing zero. I'm completely out of the loop and he doesn't even seem to consider getting me in.

But what really upsets me are the tasks he prepared for me. As he first described them they sounded somewhat interesting from a technical perspective. However, I found he had described them in such detail that a beginner student would be bored.
A description of the desired behaviour, so far so good. But also how to implement it, down to which classes to create. He even added a list of existing classes to get inspiration or copy code from. Basically no thinking required, only typing.

Well not quite, I did find something I needed to ask. Predictably he was busy. I was able to answer my question myself. He was, as it turns out, designing and implementing something actually interesting. Which he never had talked about with me. Out of the loop. Fuck.

Man, I'm fuming. I realize he's probably just ignorant. But I feel treated like his typing slave. Like he's not interested in my brain, only in my hands. I am *so* fucking close to assigning him the tasks back, and telling him since I wasn't involved in the thinking part, he can have his shitty typing part for himself, too. Fuck, what am I gonna do? I'd prefer some "malicious compliance" move but not coming up with ideas right now.

I inherited a nextjs project from an unknown guy and am fangirling the codebase

But the deeper I familiarise myself with it, the more the cracks begin to appear:

1) The dude Is incapable of grasping the basics of DRY concept. He actually setup a ton of stuff I may have done poorly if I'd started working straight out of the docs, so I feel like I owe him a shower of praise. I guess being new to nextjs makes it look more impressive than it actually is. He was paid off, yet getting the credit seems unearned to me. I'm just afraid reaching out to him might turn around to bite me in the ass
***

I had the above in my drafts, contemplating sending him a token to show some appreciation for unknowingly showing me the ropes. I was going to find him on LinkedIn using his commit names. But after doing everything I've done, undergoing the anxiety and severe pressure I faced at the hands of the project owners, I'm not sharing a farthing with anybody

Yes, I may not have known about zustand and persist middleware. Yes, he did all the ui. Yes, he created the base components and fancy wrappers around form and button html elements. For those, I'm grateful

But the amount of refactoring I had to do to, for an opportunity to implement my own target features, I'd say I can lay as much claim to the project as he does.

Side note #1: I have some newfound respect for front end devs. We used to discriminate against them for doing just css but that was only relevant in the jquery days. Now, they have to use cryptic css frameworks (sass, less, tailwind), they have to learn esoteric syntax of some js framework and write controllers/components as the case may be. They have to (the worst part), bind this data to an API, which would never make sense to me coming from a php ssr-natural world

Back rewarding the guy, some of the challenges I came back from were:

1) Next server outages: I still don't know the workaround this. The app terminates, browser giving an error about using up memory. I have to wait for about 10 minutes before I can access the app again

2) spring Webflux authentication not hydrating: I was unexpectedly asked to work on the back end too, where I got tortured with this horrifying condition. The most poorly documented framework for the Web has no upto date guide on how to implement jwt security measures. I opened a question on stackoverflow. A day later, both my question and the helpful answer got downvoted

3) Zustand not retrieving any data from localstorage once page reloads, until I miraculously stumbled on a hack: there's a config callback for reading state after rehydration or thereabout. So I interact with the state there. That's the only way content clearly in localstorage can get transmuted into dynamic format accessible by the code

4) Mongo database suddenly disconnecting: for no apparent reason, this bailed. Accessible on compass. This was even when I realised it was responsible for front end requests not going through. Eventually created a new database and requests surprisingly began connecting again. Thankfully, my laravel background taught me about seeders so I had them on standby from the onset. Wasn't difficult to just port to a fresh database after confirming the first one was inaccessible to the app

After this painful odyssey and the time constraints, threats of moving forward with someone else, I deserve every dime they deem me worthy of and more

Yay, I inherited a project with no documentation that is soon to be out of the prototype phase in a tech stack where I have no experience. It is already sold to customers and they expect it soon.

There are so many bugs, never been code reviewed but the main functionality semi-works :(

Somehow, a contractor left with all our unit tests six months ago. I just inherited this project. It's 200kloc of Django spaghetti, and I have no unit tests.

Fuck inherited projects!

I was invited to work on a simple migration and integration project for a bank. Thinking it was simple and just a month long project, I accepted it.

... last August 2020.

Now, almost a year later, we have freakin gone nowhere with this project. The bank has had 5 project managers leave over the last 1.5 years that this project has been active.

And every fix I make brings in numerous other problems.

It’s so fucking insane.

No one knows who to blame.

I am currently in call with the bank with about 12 other people who are all watching me fix bugs that they find -.-

Current mood: Preparing a communication plan for how to explain why we have decided to throw out the entire 3-years-worth-of-work code base for the frontend project we have inherited and rewrite it from zero because it's just. THAT. BAD.

I need to vent or I'm going to fucking explode like a car filled with bombs in motherfucking Iraq...

A couple of months ago I inherited a project in development from our team leader who was the sole developer on it and he was the one who designed every single thing in it.

I was told the project is clean, follows design patterns, and over all the code is readable and easy.

Those were all fucking lies.

See throughout the period he was working on it, I saw some of the code as it was going through some pull requests. I remember asking the dev why he doesn't comment his code? His response was the most fucking condescending shit I've ever heard: "My code is self-documenting"...

Now that I have full control over the code base I realize that he over engineered the shit out of it. If you can think of a software design pattern, it is fucking there. I'm basically looking at what amounts to a personal space given to that dev to experiment with all kind of shit.

Shit is way too over engineered that I'm not only struggling to understand what the hell is going on or how the data flows from the database to the UI and in reverse, I'm now asked to finish the remaining part and release it in 8 weeks.

Everything is done in the most complicated way possible and with no benefits added at all.

Never in my career have I ever had to drag my sorry ass out of bed to work because I always woke up excited to go to work... well except for the last 2 weeks. This project is now taking a mental toll and is borderline driving me crazy.

Oh, did i tell you that since he was the only dev with no accountability whatsoever, we DO NOT EVEN KNOW WHAT IS LEFT TO BE IMPLEMENTED?

The Project Manager is clueless.. the tickets board is not a source of truth because tickets set to resolved or complete were actually not even close to complete. FUCK THIS SHIT.

For the last week I've been working on 1 single fucking task. JUST 1. The whole code base is a mine field. Everything is done in the most complicated way and it is impossible for me to do anything without either breaking shit ton of other features (Loosely coupled my ass) or getting into fights with all the fucking libraries he decided to use and abuse.

1 whole week and I can't even get the task done. Everyday I have to tell the project manager, face to face, that I'm still struggling with this or that. It's true, but i think the project manager now thinks i am incompetent or just lazy and making excuses.

Maybe I'm not smart enough to understand the what and why behind every decision he made with this code. But I'm sick to my stomach now thinking that I have to deal with this tomorrow again.

I don't know if I'll make the deadline. But I'm really worried that when this is released, I'll be the one maintaining that nightmare of a code base.

From now on, if i hear a fucking developer say their code is "self-documenting" I will shove my dick + a dragon dildo + an entire razor gaming keyboard up their ass while I shoot their fucking knees off.

oh... and there are just a couple of pages of documentation... AND THEY ARE NOT COMPLETE.

So, after having my mental breakdown with the 500k LoC Zend Frameshit PHFuck 5.5 with 0 test project, for a whole year; and after moving to a better job, I now inherited a React/Node/GraphQL project with a shitty architecture. It's so shit technical debt can almost be payed with actual cash... or flesh, ass-for-arch.

However, line test coverage is over 90%, so I guess it is an improvement.

Angular 2+, it's just so elaborate, and over the top complicated. On larger projects it easily becomes a mess. I started a new job where I inherited a angular 2+ project, that is terribly made, it's so frustrating. I now use Vue.js 2, and it's just so beautiful, especially single file components :D

Shit
Shit
Shit
Fucking shit
Wank

Customer: The quality of the software you’re delivering is going down
Me: That’s because we’re developers, support, and spend all day on meetings without mentioning that deadlines are defined by you, not the technical team
Project Manager: I have added more members to the team so you can deliver faster
Me: That’s just slowing us down because this inherited code is shit, there’s no documentation and we’re always in a rush, without time for a proper ramp up
Customer: *throws money to our faces* I’ll remove two weeks to this delivery so we can test it better
Me: …

Our business partner just tried to deliver a motivational pep-talk to the dev team that ended up sounding more like a sermon. Instead of hearing we did a good job, we heard we could be doing a better job. Never mind that the project is rushed, lacking funding and built on an unstable codebase inherited from a proof of concept demo. I just lost all respect for the guy, who I thought appreciated how hard we've been working. Apparently he's just another administrative cog who wants to climb the ladder of success while standing on other people's hard work.

Right, no more extra miles for this project. Time to just coast on and see it sink in its own excrement.

See this far too often in our inherited project:

<?php
$stuff = "";
// ...
$stuff[] = "something";

So at one point I worked on an inherited project that had the worst code I've ever seen. I mean bad, so bad there may no quantifiable measure that can accurately convey how bad. We ended up naming the thing 'the hydra', cause it had a million issues and they just kept growing as we fixed things. To my point, in C++ they implemented their own primitive type Boolean32 as a signed int32 pointer. If that wasn't enough they used it as an octal bit mask. They also switch the value using logical and / or between 2 numbers, 037777777777 and 000000000001. So essentially they only switch this value to 1 or -1 and end up comparing it to their own const true or false. In c++ any value not 0 is == true...apparently not in this code.

Inheriting a project from a previous developer (front end stuff) where it takes more than 10 seconds for sass to compile. Like do you really need all this shit the site has bloody 4 pages.

// new Rant("help")

I am currently writing my first 'real' Ruby project. I want people to be able to contribute through a module class by extending it and implementing the needed methods. This can (if done correctly) provide new commands for the terminal and new features.

But is this a good idea? I would download the code then by using git and keep it that way updated (similar brew does). At the start of the terminal app I would add all files recursively from the folder where I clone the modules into and lookup each class that extends module and then load the new content.

Is there another way of creating such a 'modular' application in Ruby?

They way I load the modules is through the inherited method, I just add the classes (not a concrete object created with new) to a list and retrieve it at runtime.

Would be nice to get some feedback going on here, not sure if my idea is good/bad.

I fucking hate spring boot. I can go unwind and nobody would hear this but boy, does it suck. Every single thing about it is a pita. I spend 98% of time I should have used for feature implementation in JAVA, struggling and battling MUNDANE functionality of the framework that ought to be nobrainers

Today started out with a project I inherited. I don't even know whether to blame its original author but he installed a couple of funny libraries for logging. The spring app doesn't build yet gradle build completes successfully. No errors are logged to the terminal, just reams and bundles of json. WHY IS THE APP NOT BUILDING??? You want me wrangling json through that pinhole console window?

I struggle with the yml settings, none works. Eventually get rid of the package (hint, it wasn't the slf4j one). I'm able to debug app not starting now, but now live reload doesn't work

I copy configs from a previous project where it worked into this. Nope, doesn't budge. Eventually enable an ide setting but now server restarts twice after file changes. The implication is that request argument annotation no longer works! So the server just restarts and has amnesia about argument type resolution

I've been sitting here for hours, without implementing a single new feature. Everything is a painstaking, avoidable aggravation VS the "framework". Never seen anything as horrendous. No line of java code yet. I just want to send a request, retrieve parameters and verify live reload is "up and running". You'd think something as low level as this shouldn't take more than two minutes. Alas, welcome to the incredible world of spring development

Why include a linter if you're just going to ignore it!

I just "inherited" an angular app from a year ago for a project that was put on hold, and after opening it in VS Code practically every TS file went red. Almost every rule in the config was not followed. Might as well have just disabled the darn thing?

The original developer is MIA so I can't contact him and ask him why either.

Inherited a project with random include '*.php' and mysql_* functions littered everywhere, this will be fun 😀😂😐😔😞😭

Inherited a project from my lecturer. He's been working on it since 2014. Over 200 classes and not a single line of javadoc. He's even written his own library code for things like task executors. Sometimes I wonder what obscure deity I pissed off in my past life to deserve this 😂😥

Not a horror. I'm rewriting services.

It started as a help request. I was asked to help with completing a service dealing with push notifications which was a research prototype. It was suggested to keep core part of it, but it was so awful that I just removed all files and wrote the service from scratch.

The second service had been developed for more than a year by a junior and then by our manager who wanted to complete it as fast as possible, without taking care of code quality. Then I was asked to take over the project and after some time I agreed with one condition: I'll have 1 month on takeover. But when I looked at the code, it became clear that it's much faster and better to rewrite everything except API and database than to takeover existing code.

The third service dealing with file exchange was working, but the junior who wrote it advised to rewrite it because it was a very simple service. So, I initiated rewriting, designed a new API and reviewed the final result.

And now I'm dealing with the fourth one. It was developed in my team but not under control. Now, when I "inherited" this complicated project, I decided to rewrite it because it should be simple, but it doesn't. It features reflection, layers inside layers, strange namespaces, strange solution structure. And that's after months of refactorings and improvements. So, wish me luck because I want to keep part of the infrastructure, but I don't know if it's possible.

Partially-inherited a WordPress website today that 1) has a ton of outdated plugins (therefore causing Visual Composer to complain), 2 was upgraded to WordPress 5 without keeping the old TinyMCE editor around, and 3) uses a page builder that's built into the "page options" portion of the Edit view.

We also have to add a couple of pages with the project in this state.

(For those not familiar with WordPress, "Page Options" can't be previewed before the page is published/updated, even though anything inside of the actual content area can.)

We got some work to do. 😐

As an android dev when I inherited a shitty project thats when I realized what really means to write readable and most importantly testable code. Codebase I inherited wasnt even really that bad it was quite readable, but boy it was not suited for any unit/instrumented tests. im talking spaghetti code.

Nowadays I refactor apps to make sure they are testable instead of spending weeks writing tests for a shitty codebase which was done without thinking about separation of concerns. Clients hate the extra couple weeks on top of request but what can I do, if they want tests they need to work with TDD approach or give extra time for refactors.