#productivity

The ONE search you should perform before you start learning

Introduction As software engineers, there is quite often a need to learn a new programming language, framework or library so as to use it in a new project or enhance an existing codebase. Continuous learning is integrated into our workday and often times it requires time after work (evening or weekends) which can turn out to be a dull process and add to an already growing burnout feeling. It is obvious that we always try to optimize this learning process, to have better results. ...

#career #clean-code #productivity

The 14 habits of highly effective developers (Part 2)

Introduction This is the second part of the “The 14 habits of highly effective developers” series. You can also read the first part here, or in dev.to In the first part of “The 14 habits of highly effective developers” series, we began showing the power of habits in a developer’s every day life and how can we benefit from incorporating simple yet crucial changes into our job, aiming to benefit the most and help leveling up our careers as software engineers. ...

#career #clean-code #productivity

The 14 habits of highly effective developers (Part 1)

Introduction Many believe that transitioning from an effective Junior-level developer to a mid-level is just a matter of time and experience. Truth is that the line separating these 2 kinds of developers is very thin and subjective. This article is not going to add more to the endless debate on “What exactly defines a mid-level developer”. To be honest, I firmly believe that something that can shift one’s mindset and help in transitioning one from a Junior to a Mid-level or Senior developer is habits: ...

#git #productivity

Git commits: An Effective Style Guide

Git commits are one of the most underrated features of Git. Pause for a moment and think; When was the last time you had to revert your code to an earlier point in time? Did you have a hard time finding that commit that messed up your code? Was that because of unclear, mixed commit messages? When that commit was found, did you also realize that you included several file changes in that particular commit, resulting in a headache when trying to rebase back to that commit? ...