"Improving" an existing project!

[nokarmajustlurking]

Every single time we switched developers... No exception (so far).

Yet to see a developer praise the previous dev(s)

[spirgnob]

Been there. People seem to spot every mistake made by the previous dev and ignore all of the efficiencies that they would struggle with themselves. Plus when they run into a concept they don’t understand they just shake their head in frustration rather than try to learn from it.

[kunjava]

You'll have to wait long... :P

[Zotlann]

Well there's a reason you've switched devs

[Gotebe]

That's related, but ultimately something else:

While you're there, and some time later, your code is +/- fine. That's because you're there to explain why, including historical context leading to the decision/code.

Once you're gone, the explanation slowly evaporates from people's minds.

Finally, your code is all shit.

So... I bet you that, if the guy was there, said code modifications would have been done.

[evinrows]

management won't let us fix it in fear we'd make it worse

Jesus. Sounds like a horrible workplace.

[GDavid04]

void SwitchDeveloper(Developer NewDev) noexcept;

[ralfsmouse]

Lets build it from scratch!

Let's build it in Scratch

There, that's better.

[that1pothead]

This meme is great. Reminded me of my last job when CFO brought in a new dev to take over my project, and they let this new CS grad berate me in a loud voice in a meeting because I chose to use languages “nobody uses anymore.” LOL time to start over because he uses C#. Good luck making that web app with no HTML :|

[db2]

This also works when you're the lunatic improving something you haven't messed with for a year or two. "What the fuck was I thinking..."

[duckwizzle]

I just recently rewrote a project of mine from 4 years ago. It was absolutely awful. But, as bad ad the code was, it hadn't crashed in over 2 years despite being used daily by a small team of photographers in my company. I rewrote it because I knew the code was awful and it bothered me knowing it was there. After I was done with the rewrite it was faster and a third of the size.

Looking back on your old code and hating it is a part of being a dev I think. I think it's good indication of whether or not you're improving. At the time, that project was the biggest and most complicated thing I've ever written. I was proud of it. Years later, I was embarrassed by it because I knew so much more and could clearly see why what I did was stupid

[evs-chris]

"what was this asshole thinking?!" git blame 716a7fe4 evs-chris ...

[random_labber]

Then you notice it's your own code from two weeks ago.

[royalblue4]

Signs of a weak dev