Matthew is an energetic 15 year veteran of enterprise software development and world-traveling open source educator. Matthew guides the Training efforts at GitHub.com and is author of the Git Master Class series for O’Reilly, co-author of the O’Reilly’s Version Control with Git book, co-author of the Presentation Patterns book, a speaker on the No Fluff Just Stuff tour, an author of three of the top 10 DZone RefCards, including the Git RefCard, and President of the Denver Open Source Users Group.
You’ve heard about this version control system called Git. Maybe some of your colleagues are using it. But is it here to stay, or just a fad?
We can best answer that by looking at what Distributed Version Control Systems (DVCS) like Git bring to the world of programming and authoring. There are a myriad of benefits ranging from the distributed nature of Git without a central point of failure, to its focus on working locally. These benefits are made possible by Git efficiently communicating over the network only when asked and its Unix-like compositional architecture.
We’ll follow that up with a look at what GitHub, a web service focused on amplifying Git for easier collaboration, brings to this rapidly changing domain of software creation tools.
This talk will enable you to sling the basic Git and GitHub lingo around like an old hat when you get back to the office.
Continuous delivery is the current buzz, but let’s take a few minutes to demystify it. 1. Does it work? 2. How would you go about getting towards that mode of operation? 3. Why would you want to have continuous delivery? 4. What tools facilitate this? You’ll leave a transformed developer. The idea of releases being non-stressful and able to be merged in on Friday at 4pm is attractive to the majority of us who have suffered at the hands of the “awful rollback” and the “long weekend.” These travails are partially the result of being on the opposite end of the spectrum from continuous delivery. Come with an open mind to branching strategies, feature toggles, and Readme-driven development.