Programmer Humor

19276 readers

2820 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 1 year ago

MODERATORS

Feyter@programming.dev

anzo@programming.dev

BurningTurtle@programming.dev

pylapp@programming.dev

513

Sometimes, it's backwards (sh.itjust.works)

submitted 18 hours ago* (last edited 18 hours ago) by 0x4E4F@sh.itjust.works to c/programmer_humor@programming.dev

137 comments fedilink hide all child comments

you are viewing a single comment's thread
view the rest of the comments

[–] ByteOnBikes@slrpnk.net 6 points 13 hours ago* (last edited 12 hours ago) (1 children)

. I think to be a good software developer it helps to know what's happening under the hood when you take an action.

There's so many layers of abstractions that it becomes impossible to know everything.

Years ago, I dedicated a lot of time understanding how bytes travel from a server into your router into your computer. Very low-level mastery.

That education is now trivia, because cloud servers, cloudflare, region points, edge-servers, company firewalls... All other barriers that add more and more layers of complexity that I don't have direct access to but can affect the applications I build. And it continues to grow.

Add this to the pile of updates to computer languages, new design patterns to learn, operating system and environment updates...

This is why engineers live alone on a farm after they burn out.

It's not feasible to understand everything under the hood anymore. What's under the hood grows faster than you can pick it up.

[–] r00ty@kbin.life 2 points 6 hours ago

I'd agree that there's a lot more abstraction involved today. But, my main point isn't that people should know everything. But knowing the base understanding of how perhaps even a basic microcontroller works would be helpful.

Where I work, people often come to me with weird problems, and the way I solve them is usually based in low level understanding of what's really happening when the code runs.