sfeldman.NET

There’s no perfect software. If it would exist, we’d never build a newer one.

I am a big fan of productivity and for myself mouse is usually more of a drag than help when coding. While watching a presentation caught presenter using a mouse in a way I never did, and that was quite productive!

A while ago, the team I was part of had a discussion about choosing the best DSCM (Distributed Source Code Management). Two candidate back then were Mercurial (Hg) and Git. We were already using Subversion and very accustomed to VisualSVN in conjunction with TortoiseSVN. Opinions split, time frames never allowed to actually make the switch and so the question remained unanswered: which one is to go with.

For a change, this was a really interesting read.

I have looked for a book about CMS concepts and was excited to spot ASP.NET 4 CMS. As much as I was excited initially, that much I was disappointed as going through the book. Here a few things I did not find pleasant about it:

Uncle Bob did it again. Another book that is full of experience and wisdom. This time it’s not about code, it’s about being a professional developer and what it means. I really loved the book. There were so many examples that I couldn’t not to smile recalling instances from my own experience having parallels with what is described in the book. One particular sentence I really loved was about TDD:

Mercurial is a very appealing distributed source code versioning system. I used it with Google code and also for some local work when no server repository was available. Worked great. This time I wanted to go through the scenario of setting up Mercurial as a team repository with a centralized server. This would be still useful for an individual developer to have local commits (better than committing every single change just to ensure it’s captured) and would allow to push an entire change set to be versioned on the server and allow others to retrieve that change set with all the “intermediate bookmarks”.