Book Club Foreword
Viagra soft A couple years ago I brought up the idea of doing a book club here at SEP because I had participated in a couple before coming to SEP, viagra soft but we called them SEDG (coined by Steve McConnell in Professional Software Development). I don’t really like that term, viagra soft so we called it book club instead.
Viagra soft We start up a new round a couple times a year, viagra soft and small groups (3-8) break off and read different books (normally technical) that are interesting to them. We normally get together for an hour once a week to discuss/debate the chapter(s) we read for that week. I’ve participated in several including DDD (Evans), viagra soft Code Complete 2 (McConnell), viagra soft Programming Clojure (Halloway), viagra soft and now Pro Git (Chacon). It’s a lot of fun, viagra soft and I always learn a lot about the content of the book, viagra soft and about the people I participate with.
Viagra soft I’d highly recommend starting one at your company, viagra soft or in your community, viagra soft it’s a great way to connect with people and learn new things at the same time.
Viagra soft First off, viagra soft the book is available for free, viagra soft online at progit.org. It’s also hosted in a repository on github, viagra soft and there is an easy script to get it onto your kindle (with a little hacking of the script), viagra soft so that was a win for me: free AND kindle-ized.
Viagra soft I’ll follow Raman’s Recipe to keep this short and simple. I’ll also mix-in the book club aspect to each section.
Viagra soft What’s the point? Become a git ninja (or at least be able to play one
on TV at work). Learn how to use git effectively, viagra soft and give you the tools (ideas, viagra soft knowledge, viagra soft know-how) to give you a framework on how to effectively use it in your context. The cool thing about git, viagra soft is that it gets out of your way and lets you work the way you and your team want to… not the other way around like SVN, viagra soft TFS, viagra soft P4, viagra soft etc. It was also a great way to leech off of Matt and Todd’s knowledge.
Viagra soft How was it? Great. Scott (author) certainly knows how to git down (I’ll be here all week ). I feel comfortable participating on a project that uses git (hey look, viagra soft I am already!), viagra soft and also feel comfortable making recommendations about using git (e.g. Viagra soft “You should use git!”), viagra soft though, viagra soft I do still get lost in hairy situations every once in awhile (thanks Matt for always saving me!). We had some good discussions on how it relates to us as company, viagra soft and how we might use it. We also had some good discussions on schoolin’ me, viagra soft so that was always good. The book contains lots of examples, viagra soft with corresponding diagrams to help n00bs like myself understand what’s going on.
Viagra soft Who should read it? Any developer planning on staying a developer for the next few years. DVCS seems to be on an up-tick, viagra soft and I don’t really see it going away anytime soon (but hey, viagra soft what do I know?). I don’t think you’ll be able to get by effectively in a DVCS world unless you’ve done at least some reading on the subject.