How to level up as a dev!

“How do I level up as a dev in terms of quality of code written”, I ask myself this question almost all the time.

There are a couple of things that can help you improve the quality of your code. The most important thing is the other developers on the team you’re working in.

You’re going to need expert feedback from someone who knows your codebase in order to improve your code quality. Without this it’s going to be hard to know if you’re applying principles correctly. This means you’ll need a team who both write good code and perform good code reviews.

Additionally, it can be hard to write good code in a team full of people who write mostly bad code. I’ve experienced this. There’s a number of reasons for this. Firstly you’ll be left with no examples of good code in your project. Secondly, your code has to interact with their code, and it’s a lot harder to write good code when it has to interface with bad code. Finally, to be coding well in such a team you’d have to be writing code in a different style to the rest of the team. This means it’s going to be like you’re constantly in conflict with them in order to get good code written.

It’s like the old adage that you are the sum of the people you spend most of your time with. This is also true at work. If you work with devs who write good code, it’s hard to write bad code. If you work with devs who write bad code, it’s hard to write good code. Essentially you’ll adapt to your code quality environment.

How to work if people write good code before before joining the company? Not gonna lie, that’s a tough one!

Co workers is the biggest one, but there’s also self learning and deliberate practice.

For self learning a friend of mine told me to read “Code Complete 2” and “Clean Code” ( though I haven’t read the book yet but I’ve got the ebooks on my PC ). These books focus on the code without regard to language used, which is exactly what you want. Good code transcends language. Also watching videos from the likes of Robert Martin could be good.

After learning must always come deliberate practice.

You may think that you’re sat writing code as your day job, so that’s deliberate practice. No. Well at least, not quite.

Yes you write code, but you need to focus on practicing writing better code. This may include things you do not have time for in your day to day work life, such as rewriting some code multiple different ways to see which one works best. You can only really do this outside work with the aim of writing better code, not the aim of shipping a feature. Let any books you read and videos you watch guide your practice, but a good starting point would be just that, writing the same code in different ways to get a feel for what works best. Then apply what you’ve learned on a real feature.

I just felt someone might be needing it and hopes it helps.

Why not come to Sales Leadership Conference 2020 on March 6th – 7th, where you would meet top C-level of all industry, even in tech and let me tell you I will be there. Please kindly visit the link to get more details.

Share on facebook
Share on google
Share on twitter
Share on linkedin