this post was submitted on 30 Dec 2024
651 points (98.7% liked)
Programmer Humor
19871 readers
178 users here now
Welcome to Programmer Humor!
This is a place where you can post jokes, memes, humor, etc. related to programming!
For sharing awful code theres also Programming Horror.
Rules
- Keep content in english
- No advertisements
- Posts must be related to programming or programmer topics
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
well this happens because people have zero understanding of what programming is. they think that programmers have memorised some "dictionaries" that translate human specifications to machine code with complete disregard for problem solving and design part of things.
when actually everyone knows engineering is all about being able to negotiate precisely which snacks and soft drinks go in the office break room
It's a delicate balance!
As a manager of developers - that's not all I do...
But I mean...yeah. That might be the most important thing I do - at least before my team was fully remote...
t've always wondered, why lots of people think that if something you do is technical, then it's inherently not creative? You sure have a bit lesser degree of self-expression, but self-expression is mere an aspect of creativity
Its easy for a passerby to appreciate the work, skill, and creativity that goes into a painting or song. Its hard for the average person to infer those things looking at an electrical box or a plumbing network. An electrician knows when they're looking at good up to code wiring and a plumber can tell if the plumbing can be put together right. Those are things the average person has no concept of and doesn't want to think about all unless they have to. One provides instant artistic appeal while having no practical value, the other provides practical value but its systems are too complicated for the average person to appreciate in totality.
yeah, seems about right
Mathematicians: "First time?"
Can you blame them? Last month my colleague (we’re both developers) pointed out how fucking deep we got into the woods of the “What if”s and “What should happen here”s of a feature that looked dead simple on its surface.
I love and hate in equal measure the hubris with which one regards a "simple" problem that turns out to be very difficult. I love it because it usually ends up being productive eventually. I hate it because it's hard to emerge from the rabbit hole once you've committed to it.