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 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.
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 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.
Yes, me too! But, only if I have the autonomy to improve things where I can. Otherwise, I just find it demotivating
Is there a generator for these?
Just use the paint, internet person
Bu-but we’re programmers
There are a few from a search, this one came up with a GitHub repo. https://arthurbeaulieu.github.io/ORlyGenerator/
Do you have more of these memes? I’d like to see more.
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.
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?
There should be a “saving thirty minutes in reading documentation by spending two days debugging a GPT generated method”
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.
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