The Right Level of Attention to Detail

I’ve been accused from time to time of not having enough attention to detail, or letting some things slip through the cracks. That is why when I notice something slipping through the cracks, or some detail being out of place I get concerned. The theory is, if I’ve spotted it, what else is wrong.

Of course, there are some things that I am overly obsessive about in my professional career:

  • Structure of version control trees.
  • Naming conventions used for projects within Visual Studio solutions.
  • Templates used for SharePoint sites.
  • Names used for build definitions for Team Foundation Server.

That is just a few of them. Of course, someone could probably write a book about the things I don’t care about when it comes to home life…


7 thoughts on “The Right Level of Attention to Detail

  1. Mitch Denny Post author

    Thanks for your views. Readify is in the business of providing solutions to our customers, whether it is through consulting services, training, solution design and implementation.

    Readify operates on a fairly flat structure which means that everyone gets involved at an operational level. So its not uncommon for me to get involved with bidding for work, scoping projects, helping come up with overall solution approaches and design, and potentially even debugging performance issues.

    Unfortunately I’m not qualified to help with the issues that you have.

  2. wal

    Mitch, would you care to further elaborate on the following:
    # Structure of version control trees.
    # Naming conventions used for projects within Visual Studio solutions.

    or point in the direction of a good article (pref. one you agree with!)

  3. Mitch Denny

    Hi Wallace,
    We do have the following resources on the Readify web-site:


    When using TFS as the version control repository this is what we tend to stick to, particularly for our solution development projects.

    As far as project naming conventions we haven’t published any guidelines and they do tend to evolve. But the best thing to do is ask what kind of projects you have – and what are the accepted norms for those project types.

    I used to use a pattern that said – if it is a class library the project should be named Company.Product.Component, if it is a web-site it should be ProductWeb, a WPF application – ProductClient and so on.

    These days I’ve change a little bit and I say that if it is a .NET-based project (web, client, class library or whatever) then use namespace style naming.

    I haven’t decided whether I like things like Company.Product.Database for *.dbproj projects yet. Seems a little bit pointless to force everything to following namespace conventions.

    Its an interesting discussion too because there are some very real limitations on how long your file paths can be before you run into the 256ish character limit.

    With that in mind maybe it is better to give all the projects themselves shorter names. Such as “Core”, “Web”, “Client” or “Database”. Then within those projects explicitly define the output name to the fully qualified DLL name.

  4. Kurniawan

    Hi Mitch,

    Do you have other technical resources /standard / best practices inside the company which can be seen publicly ?


  5. neil

    gday mitch – been a while since I caught your posts…
    CTORoleDumbedDown should be in the bideloneon navy… he’ll die and his peers will all drown digging his grave.

    For those serious enough… the best practices for use of the products are in the SDK notes of all Microsoft Products… or on MSDN … or in fact in the university faculty libraries with addended footnotes from faculty staff…

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s