I might be in the minority, but I get more excited about the idea of maintaining/working on some creaky old legacy code base than I do about the idea of starting a new project from scratch.
I enjoy this too, but it’s kind of rough when you’ve inverted control, teased apart unnecessary coupling, updated dependencies and backed everything with unit and other tests, but then your colleagues are too scared to code review it.
I find that working on production code with well defined use cases and requirements to be the most satisfying, and working on new proof of concept / demos / marketing tools to be the least satisfying.
So on balance, more of the legacy projects I’ve worked on have fit those criteria than the new builds, but the couple of new builds that had well defined use cases, and no legacy code to deal with were the absolute best.
What fucking ass for brains engineer wrote this dogshit code!!! I’m gonna scroll back to the header find out who wrote and give a piece of my mind to… myself x.x
I might be in the minority, but I get more excited about the idea of maintaining/working on some creaky old legacy code base than I do about the idea of starting a new project from scratch.
Is there a generator for these?
There are a few from a search, this one came up with a GitHub repo. https://arthurbeaulieu.github.io/ORlyGenerator/
Just use the paint, internet person
Bu-but we’re programmers
Do you have more of these memes? I’d like to see more.
Shared this with my team just recently. Guess there is a lot more of these brilliant edits.
Nice! Thanks. :3
Is there a bigger resolution btw?
deleted by creator
From the last time this came up I got most of them from this guys collection.
https://lemmy.ca/comment/11139658
Nice collection. Thanks! :)
Thank you for this.
Yes, me too! But, only if I have the autonomy to improve things where I can. Otherwise, I just find it demotivating
I enjoy this too, but it’s kind of rough when you’ve inverted control, teased apart unnecessary coupling, updated dependencies and backed everything with unit and other tests, but then your colleagues are too scared to code review it.
Feeling of deleting lines > Feeling of adding lines
Ha, turns out there’s one for that
I find that working on production code with well defined use cases and requirements to be the most satisfying, and working on new proof of concept / demos / marketing tools to be the least satisfying.
So on balance, more of the legacy projects I’ve worked on have fit those criteria than the new builds, but the couple of new builds that had well defined use cases, and no legacy code to deal with were the absolute best.
also, your own code after you’ve spent time away from it.
That is the strangest thing, going back into a program and thinking “what the hell was that guy thinking?” and then realizing it was me.
What fucking ass for brains engineer wrote this dogshit code!!! I’m gonna scroll back to the header find out who wrote and give a piece of my mind to… myself x.x
git blamegiveth andgit blametakethThe time varies but starts at about 1 day for me…