Used to do that when I was working in science. I also kinda loved it. Just interesting to intimately experience how people thought back in the 80s. There are surprisingly many Fortran 77 libraries still in use today (they can be called from modern Fortran code).
I’ve gotten to spend some time where my major responsibility was to refactor and improve “research-grade” code from some scientists. Felt like tending a Zen rock garden, but code lol, I found it really relaxing and lovely.
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.
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.
You are not logged in. However you can subscribe from another Fediverse account, for example Lemmy or Mastodon. To do this, paste the following into the search field of your instance: !programmerhumor@lemmy.ml
Post funny things about programming here! (Or just rant about your favourite programming language.)
Rules:
Posts must be relevant to programming, programmers, or computer science.
No NSFW content.
Jokes must be in good taste. No hate speech, bigotry, etc.
I love doing that…
I dive into Fortran77 code regularly. Sweet mother of Neptune! All caps and such short variable names!
Used to do that when I was working in science. I also kinda loved it. Just interesting to intimately experience how people thought back in the 80s. There are surprisingly many Fortran 77 libraries still in use today (they can be called from modern Fortran code).
I enjoy refactoring and making legacy code better.
Same.
It’s as close to being a doctor as I’m gonna get.
I’ve gotten to spend some time where my major responsibility was to refactor and improve “research-grade” code from some scientists. Felt like tending a Zen rock garden, but code lol, I found it really relaxing and lovely.
also, your own code after you’ve spent time away from it.
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 blametakethThat is the strangest thing, going back into a program and thinking “what the hell was that guy thinking?” and then realizing it was me.
The time varies but starts at about 1 day for me…
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
Feeling of deleting lines > Feeling of adding lines
Ha, turns out there’s one for that
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.
There should be a “saving thirty minutes in reading documentation by spending two days debugging a GPT generated method”
Nice! Thanks. :3
Is there a bigger resolution btw?
From the last time this came up I got most of them from this guys collection.
https://lemmy.ca/comment/11139658
Thank you for this.
Nice collection. Thanks! :)
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/
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.