In the last blog post, we looked at our local development environment and how the complexity of modern stacks made it challenging to setup correctly.
In this post, we will look at the second step of path to production, the version control system, and the advantages and best practices around using tools like Git.
The first step of the Path to Production starts from our development environment, as the rest of the stages it changed quite a lot in the last ten years.
I clearly remember how I was coding during high school, from the Z80 suitcase where we would enter HEX instructions in the Numpad to Pascal, C and Borland Delphi.
Machines had a fraction of the power or memory or storage they have now, and yet the software I was able to build with Delphi was pretty impressive (for the 17 years old me), and I felt very productive.
You may have heard of Release Management, which refers to the process of managing, planning, scheduling, and controlling software builds through various stages and environments. This includes testing and deploying software releases.
In recent years, a new term has emerged called Path to Production.