For those of you who don’t know me, I’m Eric Amodio, creator of GitLens. I’m an innovator, leader, architect, and seasoned full-stack developer. I started developing GitLens way back in 2016 when I fell in love with Visual Studio Code and wanted to play with what was then newly released extension support. It all started with a simple question: could I add Git insights via CodeLens (hence GitLens) to any document? Which of course was yes, and a whole lot more.
Infrastructure as Code (IaC) is the practice of recording the desired state of your infrastructure using a declarative language. In this article, I’m going to assume that your team is starting from scratch. Maybe some of your build process has been scripted, and maybe there is some manual testing and quality assurance work happening. Many readers will find that they are midway through the IaC adoption journey I’ll describe, or that they have missed some steps.
With the rise and advancement of technology and artificial intelligence, there is no question that new rationalists are joining this group to enforce their ideas. However, most Rationalists and highly successful people do not hold back anything, and maybe this is because the technological and financial industry embraces disruptors of the norm. One rationalist concept adopted by the technology and financial sector is Fintech.
