this post was submitted on 22 Oct 2024
228 points (86.5% liked)
Technology
59377 readers
2559 users here now
This is a most excellent place for technology news and articles.
Our Rules
- Follow the lemmy.world rules.
- Only tech related content.
- Be excellent to each another!
- Mod approved content bots can post up to 10 articles per day.
- Threads asking for personal tech support may be deleted.
- Politics threads may be removed.
- No memes allowed as posts, OK to post as comments.
- Only approved bots from the list below, to ask if your bot can be added please contact us.
- Check for duplicates before posting, duplicates may be removed
Approved Bots
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
I'd rather be a bad programmer that gets stuff done than a good programmer who's just jerking off about proper design
t. good programmer
Once you move past a couple thousand LOC, you'll appreciate having an easily modifiable, modular design you had the foresight to plan out.
Or you can just trawl through thousand of lines of unstructured spaghetti code trying to figure out where to shoehorn your new feature in like a QBasic/Arduino kid.
I've never appreciated design decisions made before starting to code. I always have to refactor later when my requirements change or when I realize there's a better way to do something.
Proper design will save an epic shit ton of money when it inevitably needs to be changed or fixed.
It depends, if you work in a statically typed language you can just use a tool to refactor. I bet a ton of advice is from JavaScript programmers where it's simply not safe to do this.
My first job doing JavaScript I realized the IDE's refactor tool wasn't aware that two variables of the same name were in fact a different variable. Due to how scoping works, it's hard to write a reliable tool to rename variables for JS. I accidentally introduced a bug renaming a variable.