1. Only use speakerphone if someone else needs to be involved in the conversation
2. Close your door
3.

See Part 1 – Architecture and Design

Once I have answered my list of high-level questions, I’ll review all the documentation written to this point.

Nothing gets my dander up more than seeing this (well, unless it’s seeing a production database littered with un-used (or test) objects, but more on that later):

$/Project
$/Project/source
$/Project/source/Released 2003-09-01
$/Project/source/Released 2003-12-10
$/Project/source/sub-project
$/Project/source/sub-project2

Ok, in case you don’t see what I’m getting at, this project should look more like this:
$/Project
$/Project/source
$/Project/source/sub-project
$/project/source/sub-project2

See those “Released” projects?

I have created a new category: Experience Counts.

One of my projects at work is to write a semi-public web service.

Isn’t it amazing what some people don’t know?

Have you ever talked to someone that’s supposedly been doing something (programming, network admin, etc.) for a long time, but that don’t know really simple stuff?

I had that experience today.

All projects start with, at the very least, a list of requirements; things the solution MUST do.

Damn, Alex really lays the smack down in this post about VB6.

The last paragraph says a lot:
”Lastly, I’ll comment on the whole situation and what I’d like to see. I feel very sorry for the folks who don’t want VB6 to go away because they don’t want to learn a new programming language and base class libraries. I feel sorry for the folks who resort to FUD about VB.NET because they are so far behind the new technology that they feel they have no other course (Moving from king of the hill to the bottom of the hill isn’t fun is it? You have no one to blame but yourself.). I would like to see Microsoft kill all new development of VB6 but I would like to see them extend the lifetime of VB6 support for ten years. I think this will largely be a non issue in ten years and I think that it does make sense to let these companies continue running their existing VB6 applications with support (they can run them as long as they regardless of course). “

It’s 2005 people.

Quick note: Part 1 of my “design and architecture” series is almost done.

In previous posts, I’ve talked about (and posted) some CodeSmith templates I wrote to generate my stored procedures, data access layer and my initial business layer.