markdown guide

I like to structure my tasks in small and quick ones. When I define my variables and functions I like to make a schema / work flow of how everything should happen and try to take the keywords of subjects and represent them as variables and the verbs to be the functions. If I take one out of the context and it doesn't make sense, I need to improve it by making it more explanatory. If at least 2 of them are simmiliar I get to the conclusion that something is wrong in the previous work flow and go back to the previous step. It's time consuming, but on a long run I found it being pretty useful.


Wow Alin, that's very systematic, I am going to try this.


When I can't come up with a good name for a function, I just call it kevin. Usually, after working a bit more on the code and using the function I have a clearer idea of the purpose of the function and I can come up with a better name.

Either that or a colleague suggests a better name in the code review.


There is no hack, naming is the most difficult aspect of writing software.

Back when people still read books, I would recommend Domain Driven Design as a deep-dive into the power of picking the right names when writing code. In today's frenetic hype-driven anxiety-fueled zero-attention-span explain-it-like-I'm-five world, however, I don't have much to say other than, "Names are hard."


Hi Neil, Thanks a lot.
Checking out the book

Classic DEV Post from May 21

Ten Cognitive Biases to Look Out For as a Developer

Cognitive biases can be viewed as bugs in our thinking. In this blog post we want to take a look at ten cognitive biases to look out for as a developer.

Devansh Gulhane profile image
Founded grabBlocks. Winner of Multiple Hackathons -Ola. Ex-Ola Wrote code that impacted millions. Indie Hacker. Also Hac is where software developers stay in the loop and avoid career stagnation.

Sign up (for free)