Git…
I have to say that I have really enjoyed learning git. Every project I do, I learn to appreciate it a bit more. Part of my interest is for a completely oddball reason - I like using terminal since it fits well in my workflow. I can have a prototype of an idea created that shows basic functionality of the initial goals. This is my proof of concept.
After I am at that stage then I can start having fun with it and start looking at these changes:
- modifying the code to meet a style guide
- refactoring the code to improve it’s modular nature and organization
- evaluating code efficiency
- brainstorming how the code may affect future feature additions
- improving existing features
- creating new features
- identifying time consuming processes and automating
- adding graphics
- creating a user interface
- creating a private and public portal
- adding utilities and operation analysis tools
- planning pipelines processes
- creating transition plans to move processes from one cloud service to another
- brainstorming modularity and code ownership among teams
- evaluating change processes and personnel risks (onboarding/offboarding)
Most of these items could be explored by making a branch. In many cases I might have an idea and just need a fast testing platform that I could keep if it works or throw away.
Here are some uses of git besides creating a branch:
- allow multiple people to develop code for one branch
- allow branches of branches
- allow tested and verifed code to merge into a primary branch
- update a branch’s code with an updated base branch
- revert changes to a previous commit
- checkout a concurrently developed code branch
- search for code changes from weeks, months, or years ago that may could to be repurposed or a cause of a current problem
- track project progress through purpose created branches
- store code in a cloud based system that has all past change logs included
- through cloud services, manage code through automated approval and setup processes
