31–40 of 73 posts
2. Try to learn the underlying technologies thoroughly. For example, try writing a simple C compiler and linker. That will teach you about a lot of things that a lot of the programming world sits on top of.
I get better at coding by coding. No, really. You can read all the books, blog posts, open source code samples you want, but nothing will substitute writing code. I maintain a handful of side projects as well as write code daily for my job. Plus, I love it. Also, my side projects usually encompass something I have no idea how to do, which quickly elevates my skill level. I love learning, so it works for me.
I get better at coding by coding. No, really. You can read all the books, blog posts, open source code samples you want, but nothing will substitute writing code. I maintain a handful of side projects as well as write code daily for my job. Plus, I love it. Also, my side projects usually encompass something I have no idea how to do, which quickly elevates my skill level. I love learning, so it works for me.
I think I "read" about programming for something like 15 years (books, blogs, HN, proggit, irc chat) I started actually coding seriously and properly the past 1-2 years. Easily learned a hundred-fold more by doing it, literally. I think too often I told myself I'm "not good enough to make something serious". And you know -- it was probably true. But that doesn't matter . Just start, things will fall into place, somet…
it's not true, most "serious" things aren't that difficult or complex
That worked for me.
Earlier quoted context omitted.
Code reviews help a lot with that. At my current company we don't review so I've found myself getting complacent
I've found this too - I work much better when I know someone I respect will read my code.
1. Write code for side projects 2. Read others code for similar projects in same language. On #2, for example, if you are working on a todo list backend in python, try to find existing solutions for todo list backend in python. Then you can see what others using in their solutions and try to bring them into yours. I understand, this approach is not applicable for everything but I have found lots of gems this way.
Only when you get stuck and cant figure something out with your current knowledge set, should you venture to look at others solutions.
Or after you have completed your solution and are curious about what others have done. You might find a library that makes your life way easier, but had you started out using that library, you wouldn't have the best understanding of the nitty gritty details.
I will admit sometimes I get a little ambitious with what I want to do and end up looking at other solutions to see just how complex we have to go.
... and then suffering through withering dismissals of my urgent questions on stackoverflow and also facing condescension, ridicule or getting ignored by people who can help me at work. Seriously.
I get better at coding by coding. No, really. You can read all the books, blog posts, open source code samples you want, but nothing will substitute writing code. I maintain a handful of side projects as well as write code daily for my job. Plus, I love it. Also, my side projects usually encompass something I have no idea how to do, which quickly elevates my skill level. I love learning, so it works for me.