DEV Community

Robert Fish
Robert Fish Subscriber

Posted on

How to be a better developer (both in the terminal and out)!

I'd like to start this off by putting a prefix on everything. This is all subjective and my own opinion. No matter where you look, there will be some shared tips and new ones so take each one with a grain of salt.

Think before you code

A simple but useful tip. This tip gets overlooked quite a lot because of time constraints(trust me, i've been there too) and lack of forward thinking but the ugly truth is. Without planning, those deadlines will creep up on you alot faster so think ahead and plan a-little and what you need to make and how that thing will work with everything else.

Look at all sides

While you look at a button that toggles something and think simple. The user on the other hand thinks the exact opposite. This is because you got to have that consideration for how the product is made and how the product will be used. If the interaction is clunky and unusable then you haven't done your job right.

Write code that solves a problem, not creates one

This is a fairly simple concept yet alot of us are guilty at making this mistake. We write code that solves one problem, yet creates 3 issues at the same time. With every line of code, think about how this solves the problems without repercussions, if you come out of this exercise without creating headaches for someone else or yourself for that matter. Then you've done your job right.

Document it and people will follow suite

A huge hate for alot of us is writing documentation. I know what you're thinking. Boring, useless, waste of time. I get that but at the same time, you know what makes a good product? Good documentation! If your product can explain itself easily in your documentation then more devs will adopt it and use it. It can be a few comments or a whole sentence explaining a function. No matter what it is, you're helping your fellow dev understand your code which makes their life easier and you can take ease knowing you've written quality code and documentation.

So that's it for now but let me know in the comments which one you have to adopt this year. Good luck 😃

Top comments (0)