Monthly Archive: December 2017
This a a great podcast with Kyle Simpson, where he talks about about his personal habits and how you can become a better developer:
I think the most important points are:
- Truly understand the problem, before you try to fix it.
- Have a very good understanding of the stack you are working on, and a good enough understanding of the abstraction / layer below.
- Make sure you can explain your code. If this is not easy enough, the code probably needs refactoring.
- Find the right balance between YAGNI (you ain’t gonna need it) and a higher level of abstraction. Don’t do premature optimisation.
- Don’t be stuck for too long, when you don’t understand something, but also don’t jump on
I’m using VS Code for my private projects and IntelliJ at work. Coming from Eclipse, I’ve never really took the time to check out all the features of IntelliJ, instead I just started using it and learned as I went along. As soon as I knew how to do all the things I needed for my daily job, I settled and didn’t make any effort to further optimise my workflow and productivity. The things I knew were just good enough to get the job done, but I wasn’t very efficient. When I did pair programming with colleague recently, I saw that he was much faster as he really used the IDE to help him achieve what he wants. I decided …