The first time I was introduced to version control (especially git), I only think of version control as an application that helps me to store the history of my code. So when bad things happened, I can see the history and revert back to the last state of “good code” in my repository.

Not until I use it more frequent, I learn that it’s more than a version control, it also a collaboration tool where you write a history of your repo journey and share it with other developers. That’s when I learn the benefit of having a good commit message can make you collaborate better with others.

In this post, I’ll share how to write a good commit message can help you be a better developer and how conventional commit, a recent convention that I learn and use can make it even easier to write a better commit message.

In my previous post, I have briefly describe my current python development workflow using a combination of virtualenv, pyenv, and pyenv-virtualenv. It’s been great for me and serve my workflow very well. But recently, my colleague at work, introduce me with a package call pipenv. I look into the website and, it seems promising in terms of makes my workflow more convenient.

I’ve been using Python programming language professionally for a year now. Previously, I only use python mostly on my uni assignment or some side project work using Raspberry Pi. Since the first time I know python, I have been used a combination of virtualenv and virtualenvwrapper to manage my local python virtual environment and set up my python development workflow. If you are not using virtual environment on your development workflow, I suggest you to start using it because it will save you with many problems in regards to package versioning and also makes your system environment clean.

With the recent #Spectre/#Meltdown event I decided to do a clean install to my early 2015 13” macbook pro. I have a couple of times did clean install for my laptop, it’s interesting because you can always have a new initial setup for every clean install that you did. In this post, my initial setup for new macbook or a macbook with a clean os installation.