Continuous Integration vs Feature Branches
I have been thinking a lot about Continuous Integration versus Feature Branching. I put together this little chart of the pros and cons.
I have been thinking a lot about Continuous Integration versus Feature Branching. I put together this little chart of the pros and cons.
Git gives you great freedom when it comes to branching, but how do we make sure that we are using that freedom responsibly?
Keeping your code always ready to ship while still being able to add new features is difficult. The Keystone Pattern can help.
It is possible to be both be productive and have fun. Writing documentation is often netiher. Antidoc can help with that.
Branches are technical debt. At some point they need to be merged back in. If branches aren’t the answer, how do we make changes?
Lot’s of people throw around the term CI/CD, but what does it really mean? What are the underlying principles and what are the benefits?
Using the CLI can be painful for some. I have found that using Oh My Zsh and Powerlevel10k actually makes it enjoyable.
Listening to a podcast and heard: “You would never put a kid on a bicycle without a helmet, so why teach someone to code without tests?”
If you are building test systems, 3-d printing is a useful skill to have. Here I talk about my experienc getting started with 3-d printing.
Don’t miss the GLA Summit. Be sure to stop by our booth and register for our giveaway as well. See you all there.