The Git Flow Branching Model
I’ve been working on a side project where I’m close to placing it in “production” (though it feels like it’s taking forever). I’ve been using Git and Bitbucket to save different project phases (I found a great explanation of Git and Github at https://blog.red-badger.com/blog/2016/11/29/gitgithub-in-plain-english).
I wanted to follow a decent Git branching strategy, so I carefully reread Vincent Driessen‘s original 2010 article about it.
There have been many different implementations of the”Git Flow” approach. I prefer to use Git directly than using an abstraction layer on top of Git so that I can better understand what’s going on. I looked around, and Driessen’s article still stands as the most unambiguous step-by-step approach.
Fatherhood and Side Projects
I came across an interesting Hacker News thread that discusses the issues around programmatic side projects and fatherhood. Note that the actual project that is the origin for this post is not as important as the back and forth questions and responses.
My progress on a programmatic side project has been glacial (as mentioned above). For me, it’s more about accepting this and letting go of the “I should have been done with it six months ago” and being mindful of the present.
Thoughts? Feedback? Let me know: @eli4d on Twitter
eli4d.com 