Introduction

If you've reached this point, we have configured a lot of virtual machines as well as a lot of services. All have to work with one another in order for us to develop and operate much like functioning software company would. I won't try to argue with anyone whether they can do it simpler or not because they very well can. I just try to do things in a method that doesn't spawn bad habits. It's better to try to work like a big company and migrate to one when you're a small developer than to join a company and have to figure it all out from scratch.

So for the next few sessions, we will make and deploy a small application so everyone gets the gist of the development cycle. In doing this, we will configure and learn how to launch the service in ArgoCD as well as have automation set up for the service. The idea is to focus on making the product and no so much having to manage the infrastructure for it.

In the age of AI, I'm not sure where software developers will go for sure, we still need people to develop new ideas and be able to follow those ideas through.

Development Cycles

To begin, please watch the following video 'What does larger scale software development look like?'.

Clock

We will be building a simple application called Clock. You can find the code repository here 0toAlpha/clock