It's fairly hard to Google the topics of "how do we set up a repo for our team so we don't wanna kill each other?" or "how do we version and package up our code once we barf enough code into the repo?"
How to set up your code repositories is a contentious topic. I won't presume to know your exact situation but I've come across enough scenarios to give a little insight on what works and what has caused utter chaos.
Admittedly this stuff is hard and many teams just get stuck and can never put their finger on the problem. Indulge me if you will on these hotly contested topics. For our exercise, let's assume we have two teams -- the UI and API team. And since I'm a .NET developer, we'll be speaking in those terms.
Let's talk about general repo paradigm's. The monolith vs the discrete repo then see how it picking one or the other relates to a SOA application.Read More
An oft-forgotten pattern in C# is the observer pattern. The observer pattern is great for taking a step towards future-proofing your codebase by adding hooks at important spots in the lifecycle of your code.Read More
Projects near and dear to me
Umbraco is the best CMS I've ever worked with. As such I've put in a lot of work extending Umbraco along with the occassional pull-request. Umbraco is open-source and has the best community bar none.
Archetype is the most difficult and successful project I've ever attempted. This project represents fantastic collaboration and creativity while continuing to remain popular over the last couple of years. It also serves as a great example on how extensible Umbraco is.
What started as a way to help my co-workers at the University of Notre Dame assimlate Umbraco faster, has now become a nice companion to the official Umbraco documentation.
When writing Learn Umbraco 7, I decided it would be nice to write and embed markdown books with Umbraco. As a result, Bookshelf was built to fill that need.