Showing posts with label professional. Show all posts
Showing posts with label professional. Show all posts

Monday, July 02, 2007

Expanding My Source Control Horizons.

I have really enjoyed using SourceGear's Vault source control server for all my personal development needs for quite a while and I have been nothing but happy with them, I need to expand my horizons.

What I really like about SourceGear, aside from their excellent products, is that they seem to really get how to cater to the small, independent software developer. By providing a free single-user license they put themselves within reach of the developer who could not otherwise afford their product. They also are owned by an individual who really seems to know how to communicate with developers on their level. Through his blog about the daily issues of his software firm and excellent book, Business of Software, which I own and recommend picking up. Also, they support developers desire to extend their products with an automation API and a set of NAnt extensions.

But comfort breeds complacency. I need to try new stuff and see what's out there.

The world of source control tools has seen a surge of growth and even better, competition over the past couple years. The list of actively developed source controls tools, that are within the reach of a mere mortal developer, has grown tremendously and the choices are all very attractive.

So, I've decided to play around with a couple vendors that have licenses that appeal to me. So here's a brief description of what I want in terms of features and licensing.

Cheap, or at least reasonably priced, since I'm not writing packaged software for sale at this point, I'd like a vendor who has discounted licenses for open-source software developers and teams. I like to constantly merge/check-in my code to the repository so having to break flow by leaving the comfort of VS.Net is not desirable. Also, I don't like having to memorize the command-line utility, I am a GUI brat and although I've worked with services and console apps for years I prefer managing the server via some form of GUI, web-based or standalone application doesn't matter. There also needs to be the ability to integrate with CruiseControl.NET and NAnt. Also, labeling needs to be easy, branching and merging of branches should be simple operations. The creation of repositories and working structures needs to be painless. Checkins needs to be atomic and transactional, individual pieces of changelists need to be easily rolled back and commit failures cannot corrupt the repository.


I know that my needs are very MSDevcentric. Hey, it's my list, if you want stuff for whatever platform you work in then that's your wish-list. So basing my requirements off that list I've looked around and have picked a couple tools that I am going to evaluate and report on before I decide whether to just stick with Vault or begin using another tool for my everyday use.


  • Perforce

    Very attractive open-source developer friendly licensing. An excellent book that covers Perforce as a tool is The Build Master which I own and have read.


  • Subversion

    CollabNet binaries, can't beat the license, FREE! I don't own this one yet but will be ordering it from Amazon. Version Control with Subversion


  • Visual Source Safe 6/2005

    From personal and painful experience, "Blech". I inherited it at my job but it's better than everyone working off a shared folder.


  • SourceGear Vault

    What I currently use, but will list it's merits. Vault is also covered in Coder to Developer, which I read cover-to-cover but then gave away as a gift to an excellent Agilist developer when he moved on to another company. Also, I think it's where I first heard about Vault.


  • Team Server

    I love me some CodePlex, best place for MS-based OSS projects I know of but I'm going to focus on the SCM aspect.


  • Surround SCM

    The current likely candidate for replacing VSS at work.



As I work through the different tools for the next couple weeks I'll update on my experiences using those tools in my day-to-day development tasks.

Submit this story to DotNetKicks

Tuesday, June 26, 2007

Programmers Bill of Rights

Coding Horror posted an article in 2006 that proposed a Programmers Bill of Rights. I've worked at some pretty messed up places that violated all or most of these "rights". Although I know that the word "rights" was used in a tongue-in-cheek manner the point was that these things make sense. Calling it a "Bill of Rights" was meant to get the readers attention, but it's fair to call the list "Common Sense". To be fair, most of these things I'd be happy to get myself if I'm paid well enough, but somethings can only be provided by the employer, such as the quiet working conditions and fast internet connection.


  1. Every programmer shall have two monitors

  2. Every programmer shall have a fast PC

  3. Every programmer shall have their choice of mouse and keyboard

  4. Every programmer shall have a comfortable chair

  5. Every programmer shall have a fast internet connection

  6. Every programmer shall have quiet working conditions

Submit this story to DotNetKicks

Heroic Developer

Look, over in the cube. It's a nerd. No, it's a geek. NO! It's Heroic Coder. Coding longer than a puny developer! Introducing bugs and errors faster than a marketing drone can dream up the next greatest feature. HEROIC CODER!

Seriously, how long can we take it? If the manager can't plan the project based on sustainable and healthy working hours over time, then you need to push back. Just because you can work late into the wee hours of the morning and over the weekend doesn't mean you should. Take a break, go home and drink a cup of tea. Go for a walk and read a (non-technical) book. Your brain needs a break. Spending too much time trying to hack in another knee-jerk requirement is going to end up taking longer and wear you out, leading to increased mistakes and a myopic view of the problem. That tunnel-vision and fatigue will only add up to having to spend more time later debugging a rapidly deteriorating code-base while still trying to shoehorn in yet another new feature. It's a vicious cycle and it's up to you to break out of it and take on the mantel of "Professional Developer".

Heroics == Hours Spent
Professionalism == Effort Maximized

Submit this story to DotNetKicks