this post was submitted on 30 May 2025
25 points (93.1% liked)

Programming

20434 readers
419 users here now

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Rules

  • Follow the programming.dev instance rules
  • Keep content related to programming in some way
  • If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities [email protected]



founded 2 years ago
MODERATORS
 

A 16 minute read, but great nonetheless

top 4 comments
sorted by: hot top controversial new old
[–] [email protected] 7 points 2 days ago (1 children)

Honestly I find this drive towards efficiency and automation many professional programmers have quite admirable.

While I studied programming, I think I just lacked this drive altogether, and I also really loved computers and to some degree I liked un-abstracting processes a lot more than I loved abstracting them, also due to my at-the-time untreated ADHD. When reasonable, I always pick a more manual way of doing something to maintain this control and understanding of system state.

I think cybersec was a great fit for me because I just found it much more stimulating to focus on the <1% of cases rather than the >99% of cases.

There is also just something very alienating when you work in large teams where each dev only contributes a small component, a lack of knowledge about the system is not only a good thing there but an expected paradigm to create reusable code, and it's a good one I think, just not actually all that fun to write for me personally.

If I have the brains for it, I'd love to try professional embedded at some point. Maybe it's something I could be good at.

[–] [email protected] 5 points 2 days ago* (last edited 1 day ago) (1 children)

There is also just something very alienating when you work in large teams where each dev only contributes a small component, a lack of knowledge about the system is not only a good thing there but an expected paradigm to create reusable code.

No. That is to say, it might be common, it might be expected, but it is often not good. Every time I join a new team and am exposed to a new code base, I'm astonished by the amount of absolute shit code that results from reusing shit in ways that it was never build with the idea of supporting.

Why? Because someone was focused on completing a single story as fast as possible and they created a dependency they shouldn't have. And this grows and festers until you have an unmaintainable nightmare.

In order to build solid reusable code you must build it with that knowledge and intent. I'll cut my rant off there, but I recently joined a new team and the wounds are all very fresh.

[–] [email protected] 2 points 1 day ago

Oh yeah totally, I just meant more as a best case scenario where you have very well documented very specific functions with a very limited scope that are reused throughout.

[–] [email protected] 1 points 2 days ago

Lol, from the title I thought this would gonna be about Ai and so called "Vibe Coding" (what a dumb term BTW).