Day 2/100 of my DevOps Journey

Here are 9 key takeaways from the Day-2 learnings!

1. Instead of private repositories, implementing Social Coding principles allows for contributions from anybody with public repositories. The repo owner is still in control of all the changes and the code is reusable instead of building everything again and wasting resources. Open Source contributions FTW.

2. Pair Programming is when two people are involved in development. One becomes the Driver who writes the code, and the other is the Navigator who observes and provides suggestions. After 20 minutes, they switch roles and continue further.

3. Pair Programming is highly beneficial for getting higher code quality, easier understanding of the codebase, and the bugs can be found earlier.

4. Always create new repos for each component. Understanding Git Feature Branch Workflow is key. Clone a repo that you want to work on --> Local Repo --> Create Local Branch --> Push code to Remote Branch --> Create pull request.

5. Work in Small batches so you can quickly develop, get feedback, make changes, develop again. Get the loop going to increase efficiency.

6. Minimum Viable Product (MVP) is the minimal / cheapest thing you can do to test your hypothesis. It is focused more on learning rather than delivery and should get you thinking "Should I pivot or persevere?".

7. Test Driven Development: Test cases drive the design and development of the code

8. Behaviour Driven Development: Focuses on the behaviour of the system from outside in as a customer. With its approachable Gherkin syntax, even the stakeholders can pitch in the design of the code.

9. Failure is inevitable. Instead of designing to avoid failure, design to recover from it. Move from "Mean time to failure" to "Mean time to recovery".