Explore >> Select a destination
|
You are here 
|
www.bryantwebconsulting.com | ||
| | | | |
nvie.com
|
|
| | | | | In this post I present a Git branching strategy for developing and releasing software as I've used it in many of my projects, and which has turned out to be very successful. | |
| | | | |
ryanharter.com
|
|
| | | | | I recently shared how I use Git to automatically track my versions. There's quite a bit more to my git workflow than just tagging versions, though, so I'd like to dive into my git usage just a little more. One of my clients introduced me to a very popular, and useful, git branching strategy commonly called Git-Flow based on Vincent Driessen's branching model. I highly recommend reading his article, it's quite good and describes a very useful branching model. | |
| | | | |
techblog.izotope.com
|
|
| | | | | Nick Donaldson Version control is an indispensable tool in modern software development, and Git is one of the most popular and widely used version control systems available today. However, despite its pervasiveness, many development teams do not use Git to its full potential, often due to a lack of a well constructed and adhered-to Git... | |
| | | | |
claritydev.net
|
|
| | | Lately, I have been asked increasingly often for some tips on how to become a self-taught developer, so I thought I'd write a post about it, reflecting on my experience and pointing out the things I'd do differently. In this article, I'll try to give general advice on how to improve for those considering or maybe already on the way to becoming self-taught software developers. It should be noted that the focus of the post is on front-end development since that's what I did; however, a majority of the advice can be applied to becoming a software engineer, irrespective of focus. | ||
