There are few areas in software engineering that get programmers and managers as actively engaged as the source code management processes. Naturally, it has evolved rapidly over the last decade or so as we went from RCS and Visual Source Safe to Git/Mercurial and SVN.
As these tools have come and gone, so also have good and bad practices. In an effort to keep up with current practices, I came across this article on using Git for source code management.
What I like about this article is its simplicity and the ease with which you can survive a corporate software development environment for product engineering.
I like to solve application problems using the Web (statelessness, hypermedia, self-descriptive representations, and uniform interfaces) to produce an asymptotically tight bound solution!