Imagine a company professing to develop for the web but lacking a site of its own. That company is either super cool, or something is very wrong. I choose to believe mine is the former, but that is a clever deception on my part.

Some people are too cheap to spend time developing their website; most are too lazy (“busy”).

What it provides is an opportunity to show potential clients what you can do when left completely unrestrained. That can be a frightening prospect, especially when the reality is that all the amazing things you can do are very much client-specific.

For example, I have no real use for a poker hand analyzer, or a flash game on my website. What am I going to do with an online inventory and ordering system? These things, while cool and interesting, are irrelevant to my business. Developing them simply for my website would not at all be worth their development time, and would in fact be disgustingly wasteful.

Also, guys, we are totally the type of people to worry or “fret” over the most comically small details, second-guessing wherever possible when in all likelihood we will hate it within a few months anyway. These are not problems that lend themselves to elegant solutions. But guys, that is fine. Some problems can’t be elegantly solved, and some shouldn’t be. Much like scheduling, problem solving would greatly benefit from perfect prescience.

What can we do but fill our pretty heads with worry as we balance requirements and resources?

Once Shaun mentioned something about blogs being boring when filled with more than 250 words. It seemed kind of arbitrary to me, but we’re at ~303 and probably exceeding any error margin due to rounding. I’ll wrap this up with the acknowledgment that this post’s title doesn’t make sense. I didn’t really get where I was going. Maybe next time?