Paul Isaris

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. ...

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: ...

This article uses Laravel for the code snippets, but the paradigm can be easily adapted to every other MVC framework out there. To make things more interesting, we will lay this article out by posting an imaginary conversation between 2 professionals: Stan, a seasoned developer, who has made many architectural mistakes (but thankfully seems to be learning from them), and Ollie, a novice developer, who just started delving into the world of serious programming and has some simple applications. ...

Introduction 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? ...

Often times, there is a need to check the size of directories or files in a project, or to evaluate the space a directory occupies in a live/development server, or just at our local machine. Here is a list of useful commands that you can leverage to make sure the available disk space of your machine is normal and that the huge node_modules directory size of your project hasn’t gone crazy :D ...