this post was submitted on 29 Jan 2025
34 points (90.5% liked)
Programming
17978 readers
397 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
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Write code, lots and lots of it. Make it really good, clean code. Rewrite it multiple times if that's what it takes to get it clean. Developing those instincts puts you way ahead of just reading about another damn framework.
And then cry when you land your first development job, knowing that you'll never get to build anything so clean and effective that will actually get implemented in the real world.
The idea is to develop keen instincts so your code comes out nice on the first try, without needing rewrites. To do that, you have to start out by rewriting a lot. You are after a fluency of style, which is somewhat independent from deep thinking. Compare being a profound musical composer who sweats blood over every note, with being a competent (not necessarily great) improviser who, given any request, can bang out something listenable immediately without too many bum notes, without thinking too hard.
Ideally you want both. Computer science education gives you the profound compositional knowledge. Improvisation needs lots and lots of practice at the basics. So code a lot. It makes everything else easier.
I would also say participate in code reviews, analyze others code from your own perspective. Depending on the quality of course, you can pick up on new concepts or approaches that didn’t occur to you when writing on your own code