Just trying to make sense of things...

Sloppy Code

Thursday, 14 February 2008 12:37 by jordan.terrell

I couldn't have said it better myself.

Categories:   Programming
Actions:   E-mail | | Permalink | Comments (1) | Comment RSSRSS comment feed

Excellent Post by Jeremy on Dependency Injection

Friday, 7 September 2007 13:23 by jordan.terrell

A very well reasoned, thought out post on the use of dependency injection:

The First Compile

Friday, 7 September 2007 11:19 by jordan.terrell

When I first create a .NET project (really any software project, not just .NET), I have a general rule that I try to follow throughout the project:

Anytime someone retrieves the project's source code, so long as they have the correct version of the compiler installed, the first compile should be flawless - no errors, no warnings.

Anytime I pull down a project/solution (open source or internal company project) and this is not the case, I already have a sour taste in my mouth, so to speak.  I've seen binary references that were not included with the source, tools needed to build that were missing, hard coded paths, and so on.

Having a continuous integration server build your project is a good way to ensure that this experience happens throughout a project's life cycle.  Plus, you don't have to deal with other developers interrupting you to ask: "Can you help me get this project to compile?"

Just something to think about...

Please, Delete Your Code

Wednesday, 5 September 2007 15:45 by jordan.terrell

I'm on a project right now that is very large and take quite the mental footprint to wrap your head around it.  This is exacerbated further by the fact that over the years (yes, I said years) that the majority of the developers who have working on the project have a fear of deleting any lines of code or code files that are no longer in use, but instead leave them in place, commented out.  Sometimes there are entire files and entire SUBSYSTEMS that have been commented out, and left to rot in the project tree.

Now, before you start to call me crazy, I'm not talking about permanently loosing code.  That would be foolish and irresponsible.  I'm talking about source code that is stored on a version control platform (e.g. Subversion, CVS, Perforce).  If your not using version control, I recommend you start using it immediately - even if you are a one-developer team. But if you are using version control, there is no point in keeping thousands of commented lines of code in a project files when you can go into version control and retrieve code that you've deleted at a later time.

So here is my plea: PLEASE, delete (not obliterate) the code you are no longer using!