966
Every Family Dinner Now (jemmy.jeena.net)
you are viewing a single comment's thread
view the rest of the comments
[-] space@lemmy.dbzer0.com 26 points 10 months ago* (last edited 10 months ago)

Writing the actual code is the easy part. Thinking about what to write and how to organize it so it doesn't become spaghetti is the hard part and what being a good developer is all about.

[-] agressivelyPassive@feddit.de 8 points 10 months ago

Question is: how many developers are actually good? Or better, how many produce good results? I wouldn't call myself a great programmer, just okayish, but I certainly pushed code I knew was absolute garbage, simply because of external pressure (deadlines, legacy crap, maybe just a bad day,...).

[-] explodicle@local106.com 3 points 10 months ago

I'm more of a mechanical engineer than a coder, and for me it's been super helpful writing the code. The rest of our repo is clear enough that even I can understand what it actually does by just reading it. What I'm unfamiliar with are the syntax, and which nifty things our libraries can do.

So if you kinda understand programs but barely know the language, then it's awesome. The actual good programmers at my company prefer a minimal working example to fix over a written feature request. Then they replace my crap with something more elegant.

this post was submitted on 28 Jan 2024
966 points (97.6% liked)

Programmer Humor

19623 readers
1 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

founded 1 year ago
MODERATORS