Skip to content


Home Made Post Cards

Note: This is categorized personal.  If you don’t want to see these subscribe to the professional category.

My son and my brother-in-law have a silly game where my brother-in-law pretends to eat my son’s feet.  Don’t ask me how it started because I don’t know.  However, my son as we were leaving started holding his feet up for his uncle to eat.  Thus was born the idea of sending my brother-in-law a post card with my son’s feet on it.

Loving a challenge, I figured out a way to create our own post cards.  First, take some pictures and make a 4×6 print.  (I don’t have a photo printer here at home since I can never make the math work out right so I had to stop by Target.) For the sake of argument, let’s call the cost 39 cents. Second, get a 4×6 index card (blank).  It cost me about 1 cent for the index card.  Third, spray mount (or glue) the index card to the back of the print.  I have no idea on a cost for this one so we’ll call it 10 cents.  Fourth, write the addresses on the back left side of the index card.  (or cheat like I did and use your label maker — it prints postal delivery point barcodes so hopefully the post card won’t get too lost.)  Fifth, write your message on the other side of the card.  Finally, add a postcard stamp to the card and mail it.  The current postal rate for a post card at 4×6 is .24 cents.

The net of this is for somewhere around 65 cents you’ve sent a cute (and sometimes strange) message to family and friends.

Thoughts on Optimisim and Pessimism

Thomas Edison was once asked about his failures in creating the light bulb and his response is often quoted as “We now know a thousand ways not to build a light bulb.”  That’s a dedication to staying positive that few (if any) of us could muster these days.  It’s a passion for creating the light bulb that would not be discouraged.
Through some of the reading I’ve been doing lately, I’ve been consumed with thoughts about how you perceive the world around you will drive how the world around you becomes.  This probably isn’t true in the literal sense (however, I wouldn’t discount it.)  What is true, however, is that we have two types of people: The optimist, always believing that there is more than their really is – but happy in that thought, and the pessimist, always believing that there is less than there really is – and miserable or fearful in that thought.
The classic is to place a glass with water equal its total capacity and ask if it’s half empty or half full.  The optimist is supposed to answer that the glass is half full while the pessimist answers that it is half empty.  A few severe pessimists, and I know some, would tell me that the glass may only be half empty now but due to evaporation, perhaps a crack in the glass, unidentified forces, etc., they’re sure that the glass will eventually become empty.  (It’s about that time that I reach over and drink it to prove their point.  It’s a fun thing to do.)
So there’s nothing new here.  You already have heard these things.  But what you may not instinctively realize is that optimism is its own reward.  Sure, I have to accept disappointment.  I’ve set the bar higher. I’ve decided to expect that things will go well, that life is ultimately good.  In return, I get to delude myself into a happy state.
And, of course, the “storms” will come, as they always do to try to convince me that the world is an ugly place.  And at those moments, I’m frustrated, disappointed, and worse.  However, that happens so rarely, that I get most of my days filled with happiness.
The mother of one of my friends is a pessimist, the kind that believes in evaporation, she recently shared with her daughter – “See, I was right.” It was in reference to some pessimistic “The sky is falling” prediction.  The answer back was the classic answer from an optimist: “So what, if you always predict something bad will happen – eventually you’ll be right about one of them.”  In other words, the optimist doesn’t have to assume that everything will always go right, they can be realistic about bad things happening, and they just believe that it’s a small proportion of every day life.
Fairly recently we were at a zoo and had our son’s wagon stolen.  We were able to recover it in relatively short order, however, its impact on our son’s small mind was fascinating to watch.  It had never occurred to him that someone would steal.  Why would you take something that wasn’t yours?  This plus trying to figure out both mommy and daddy’s reactions was putting his poor little mind into overdrive.  The end result was we got the wagon back.  He still vividly remembers the incident (perhaps too vividly.)  He has changed his behavior.  He still takes his wagon to the zoo; however, we keep a closer eye on it.  He didn’t give up.  He didn’t refuse to enjoy the zoo just because a bad thing happened – he simply is more aware of the possibility of a bad thing happening and tries to plan for it as best he can.
So my parting thought, a quotable, is simply this:
“Failure is only not trying because there is no hope of success.  Persistence guarantees eventual success through hope.”
Be an optimist, what do you have to lose?

The Tivo Out of Box Experience is REALLY bad

It is amazing to me just how bad of an out-of-the-box experience that you can have with Tivo.  For all of the good things that the product does, it’s like there’s a completely different company managing their out-of-box experience.

I wanted to summarize for folks the situation that I ran into recently when I purchased a Tivo unit with DVD recorder for the church I attend.  I purchased it to record and store content from a specialized satellite subscription that the church purchased.

To start, you must use the phone line for initial connectivity and there is still no network connection on the unit I purchased.  You can add a USB-based network card, however, it’s a separate accessory that you have to buy.  Not a big deal in the grand scheme of things, however, it can make logistics difficult as it did for me.  To get the unit started you must complete the setup calls (not setup call as seems to be the common parlance.)

So I plugged the unit into a line that I thought was an analog phone line — it turned out to be a digital phone line — and the modem burned out… when the replacement unit arrived I plugged it into the line for the fax machine (which I new was analog).  It completed it’s first call and then asked me to setup the A/V sources.  I go back to try to tell it that I want to specify my sources, since specialized satellite wasn’t one of my options.  It forces me to make the 10 minute setup call again because I transitioned back before the call to change the sources.  I get to the same screen and eventually turn the unit off and take it back to the room where the satellite is connected.  When I plug it back in it forces me to go back through the setup again — including the phone call … which I can’t make because the phone is in another room.  (Are we beginning to see the insanity?)

So I decide I’ll bring it home where I have phone and video together and then move it back to the church.  That’s great.  I start the process all over and get through the first call and the setup relatively quickly.  (I was doing other things at the same time.)  Then it goes to make a second call.  After the third failed attempt I replaced the relatively long phone cord with a short cord.  It’s still not working.  Each attempt takes five minutes or more because it doesn’t restart the download and in fact it does a cleanup activity prior to starting.  Needless to say it’s a painful experience.  I have Vonage for one of my phone lines, the one I was using.  So I eventually tried the other line and it worked … and at the end it says that the unit will be working for between four and eight hours and I shouldn’t unplug the system until it’s done.  It doesn’t indicate how I will know if the unit is done, nor does it indicate if there’s a safe way to power down the system that won’t cause any issue.

What irks me most about this whole situation is that less than a dollar could have put a flow chart of setup activities in the box.  Something that would have shown me the steps I’d need a phone line for, the overall process, and how to deal with common issues — however, that level of thought wasn’t put into the out of box experience — in a company that spends so much time working on user interfaces, ascetics, and other “user touch“ aspects.  It’s unfathomable that they wouldn’t put more thought into the out of box experience.

I’m now sitting with a Tivo unit on my desk that needs to go back to the church.  I’ve invested hours getting the unit to work for something that frankly should have just powered on, started up and let me use it as a glorified VCR without any of the issues I ran into.

By contrast, I’ve had a replay TV unit for three years now.  The out of the box experience was easy. I had the option of using either a phone or the network.  As I remember it, there was a basic set of instructions for what was going to happen and what I needed to do.  It was an extremely installation…

Now I need to see if I can figure out how to get the unit to tape from the satellite feed back at the church or if I’m not done dealing with the setup process. At least I can connect it to the network, if I can figure that out…

Rant: Book Development Editors are a dying breed

I used to do a lot of development editing for books.  It was fun work.  You were able to see the impact on the books you were working with.  You could see author’s writing getting better as they started to get used to your comments.  They would quit taking short cuts.  They would begin to view the material from the reader’s point of view.

The job of the development editor in the book process is to “develop” the material.  In other words, the development editor is supposed to make the material better.  Development editors don’t do this by adjusting the placement of the commas or the number of capatilized letters (that’s the copy editor’s role.)  Instead, the development editor looked at the tone, overall flow, depth, and other broader issues.  They focused the author’s attention on these issues so that they could be improved upon.

What I’ve realized from the reading that I’ve been doing lately is that the development editors aren’t doing this today.  It’s likely because they’re too busy with other projects but still the abscense of this assistance for the author is painfully missing from many technical books today.

The book industry is right to be scared of the Internet and the way that we consume information these days, however, they’re not doing themselves any favors by shortcutting the development process in favor of books that are quicker to market.

I read a lot of blogs, articles, and shorter content on the Internet.  However, when I really need to have a thorough understanding of a topic, or I need to make sure that the information is right, I go to a book.  I use them as authoritative voices — however, this is challenging for me when the books have no more thought or organization to them than a typical one of my blog posts.

I wonder if the technical book publishing community will totally collapse before they learn what made Wrox what it was. Ok, before they went bankrupt.  The point is, however, that the brand of Wrox was powerful.  Having the opportunity to work with them (as a technical editor), I can tell you that they crafted their books.  The development editor was very involved.  They had the material run through two technical editors.  Everything was designed to get a quality product — at the center of that effort was the development editor who was managing all of the support that they were providing to the author.

Of course, the days where you could expect that a book won’t wander — that it will follow a clear, intelligible outline are long gone … Some days, I wish I could go back.

The Tipping Point: How Little Things Can Make a Big Difference

Book Review-The Tipping Point: How Little Things Can Make a Big Difference

If you’ve been reading this blog then you know that I’ve been doing a lot of reading of my own lately, mainly associated with some professional development in the area of reconnecting to basic software development fundamentals that I’m already aware of and some new things as I try to find some new ideas in the various forms of the agile development movement that I can use or try.

The latest book is radically different.  It’s one that was casually mentioned to me by a colleague, Jeff Juday, who was recently awarded Microsoft MVP status.  He mentioned how he thought the program related to the book he had just read, The Tipping Point.

This piqued my interest initially because I’m always curious about how the market works and Jeff promised the book would have some insight.  (He was right.)  Having written (or written part of) 16 books, I know how random sales can be from one title to another.  In fact, when my friends and colleagues approach me about writing a book and ask me if their idea is a good idea, I usually respond with I have no idea.  The market seems to work in mysterious ways.

The Tipping Point is a book about epidemics.  Not so much the negative things as we associate with the word epidemics but rather about things that have a radical growth cycle.

At some point in the book, I wanted to share a passage with everyone I knew.  Some of my mentors, the pastoral staff at the church I attend, my mother, several of my friends, and some of the folks I know at the MVP program at Microsoft.  The truth is that when I finish this blog post many of them will be receiving a link via email to check it out – excluding those I know read my blog regularly and so they’ll see it anyway.

I found the book enthralling as I examined some of the market reactions I had seen.  The birth of the Internet (really the adolescence of the Internet), the growth of cellular phones (which the book discusses), and I even thought about it in terms of SharePoint Portal Server.  (For the record, I would have written this blog post even without a SharePoint tie-in.)

I remember working with the 2001 version of SharePoint Portal Server.  When I’d talk with my peers most of them would be asking me – “Share What?”  There weren’t many people that knew what it was.  Today, when I talk about SharePoint to people I meet – even outside of the industry – I get a surprisingly high awareness rate.  Most don’t know what it does exactly but they know that people think it’s something to watch.  (As a sidebar, most people who do SharePoint work don’t know exactly what it does.)

The interesting thing is looking at this pattern – and others – and evaluating why SharePoint is such a pervasive word in the IT industry and in the minds of small business owners.  It certainly can’t be attributed to the stellar marketing that Microsoft has done for the product.  (Sorry guys.)

Quietly you’ll get some of the marketing folks in the information worker group to admit that there’s a lot of confusion about SharePoint and few places to find good answers.  I’ve had clients pay for us to develop documents that they can use to internally explain the solution – because it’s simply too hard to do without clear documents on what it does and doesn’t do.

SharePoint isn’t successful because of a greater number of people running Microsoft Office.  SharePoint’s popularity can’t be explained by a renewed interest in IT.  It’s an absolute mystery to me as to why it’s become so popular.  (Here’s a challenge – tell me via email why you think it is so popular.  I’d love to hear your perspective.)

The Tipping Point didn’t explain why SharePoint has become so popular but it did give me the clues to look for to identify what happened.  I don’t have the answers but I do at least know some of the questions to ask.  In that way, I think it will be invaluable in the way it allows me to see things more clearly.

The analogy that I’ve come up with to explain it is that it’s like someone with imperfect vision – like myself – putting on glasses for the first time.  It doesn’t make me see or allow me to see for the first time but it does bring more clarity to what I’ve been seeing all along.  The unfortunate thing is that it has also exposed me to how much I still don’t see.

There are some psychological tenants that most people subscribe to – including me.  That I know believe are false.  I’m questioning how much about the way people behave is about their character and how much is about their circumstances.  (In an interesting turn of events, the environment swapping movie Trading Places was on TV last night.)

If you’re the least bit curious about how trends get started and would like to get a little bit better picture of them I highly recommend reading The Tipping Point.

Recognition vs. Recall

Where did I put that again?

One of the things that’s been fairly constant in my life over the last few weeks — that rediscovery stuff is hard, particularly when you try to do it too quickly.  It’s caused me to recognize that there’s information I’ve seen before but I couldn’t recall it on command, nor can I even remember where I saw it again.

It reminded me of some of the instructional design research I did several years ago while I was doing a lot of development editing for books.  I ran across Bloom’s Taxonomy of Educational Objectives, while I can’t say that I agree with every bit of the classification or the revision of the work.  However, it’s interesting because it causes you to think about how we teach and learn in a different way than we most folks think about it.

What caused me to think about it was the difference between recognition and recall.  These are at the bottom most levels of the taxonomy.  The most basic level is recognition.  That means that if someone asked you what it was you couldn’t tell them but if they say it to you — you will recognize that you heard it before.  Taking from my daily life…  My wife asks me to pickup paper plates from the grocery store.  I walk into the store and can’t remember what it was that my wife asked me for.  (I lacked recall.)  However, my friend, who co-manages the store walks up to me and starts offering ideas on what it might be: bread, milk, cheese, etc.  When he hits paper plates I immediately recognize that it what I’m there for.

The trick, for me, is to figure out how to get more of the stuff I read and take in into the recall category and less in the recognition category.  I could be struggling for higher levels, levels that allow me to do things with the information but for now, I’d be happy to hit recall all the time.

Excuse me while I go look for my car keys…

If you’re interested in learning more about how we educate ourselves and others, it’s an interesting read.

The sound of a million crickets longing to be free

If you’ve been wondering why my blog has been so quiet over the last 45 days or so, the answer is a bit complex. (but you can continue listening to the crickets chirping in the absence of content here.)  I need to take a break from my reading to give my brain a rest… so now’s as good a time as any to explain the pieces of the puzzle that have lead to the relatively low number of posts.
First, and foremost, I’ve entered into a “phase” of reinvestment.  That means many things but the short answer is I’m learning new things and relearning old things that I’ve forgotten – or I’m at risk of forgetting.
One of the pieces of this puzzle is the relatively large amount of software that Microsoft’s dropped at my door.  I hadn’t really had much of a chance to work with .NET 2.0 or SQL Server 2005 while they were in beta – a side effect of a busy life.  So I’m in the process of getting up to speed on them.
Just in case you’re wondering – for me getting up to speed means doing things that are a bit beyond the envelope.  I’ve been playing with configuration classes (to support non-file based configuration sources), factory classes, and generics.  I’ve not gotten done yet, however, this will be the foundation of the new web site that I’m building.  (Don’t ask when it will be done, I don’t know yet.)  I’ve also been playing around with master pages and web parts … I’m trying to mesh those into a foundation layer that allows me to control what’s on the page from a database.  … and don’t even get me started about the HTTP handler to allow Google to walk around the foundation without getting aggravated by query strings.
Couple that with “Office 12” and Commerce Server Betas.  Office 12 contains SharePoint which is one of the things driving a great deal of my work these days.  Commerce Server is near and dear to my heart for many reasons not the least of which are that it’s at the core of the new web site I’m putting together and I’m a Commerce Server MVP.
Because I’m preparing to embark on a relatively large software development project, I’m reminding myself how to do things right.  That means rereading Steve McConnell’s Rapid Development book, Fred Brook’s The Mythical Man-Month, and a few other Software Development Practice books.  I’ve read them all before, but I felt like having read them about 10 years ago made it time to reread them.  (I highly recommend both of the above books – both are “dated” but they illuminate some core concepts and problems that don’t seem to change.)
I’m also reading Karl Wiegers’ Software Requirements, Second Edition.  I’ve had a few projects recently that somehow managed to skip the requirements phase of development (in whatever lifecycle model you want to call the projects.)  So I thought reading it would remind me of what a project with requirements is like.  The book is solid, though somewhat repetitive.  It’s much like a buffet where you take what you want – though I miss the carefully coordinated entrée and sides.  My personal task for the end of the reading process is to try to distill the information into a one page cheat sheet I can laminate to remind me of the core concepts.  I find that requirements is the one area where continuous reminders is helpful for me.
When I get done there I get a chance to read some books on Agile development … I’m looking forward to getting a firmer foundation for what Agile is supposed to be – presuming that the two books on the topic that I have can do that.
The second factor for the lack of posts is that I’m doing some infrastructure cleanup tasks.  I run my own network infrastructure – I suppose that my MCSE and my former MVP aware for Windows Server-Networking will die hard.  There have been nagging little problems with the infrastructure for a while – errors that weren’t causing any real problems but were still getting thrown to the logs.  Well, in an effort to get my Pocket Pc Phone edition working with direct server synchronization, I had to clean up more than a few of those errors.  (By the way, My QTek 9100 Windows Mobile 5 [Pocket PC Phone Edition] rocks.  The over-the-air sync to Exchange is amazing.)
The third factor is that I’m building an arcade style kiosk for my son.  It will house his PC.  It will be like the old “Pac-Man” arcade games but slightly wider to accommodate the keyboard, mouse, and joystick.  It will have a real coin door which will eventually allow you to turn on and off the PC as well as an overhead light.  The coin door itself has been installed, I just haven’t finished the electrical for the switches.  Because my son is only 4 (as of January 5th) I’ve also built a seat arrangement that slides in and adjusts up and down so we can get the seat setup at a reasonable height for him.
The net effect of this project is that it’s taking a ton of my time.  I’ve begun referring to it as the albatross around my neck.  However, I saw the light at the end of the tunnel today as all of the major components have been assembled – I just need to get it in the house and hooked up and I’m going to take a break from the project for a while.
The fourth factor is that my writing schedule has been slowed WAY down.  Basically, I’ve temporarily discontinued my regular writing.  I expect that I’ll start writing about software development issues again very soon – however, in the mean time that means that even the regular posts linking to my articles have been missing.
The fifth factor is that I’ve been working a ton of hours at the church.  I took on leadership of the technical ministry for worship services which means I’m responsible for coordinating sound, lighting, and media.  Of course, I’m trying to get everything documented and get a better fundamental understanding of each part so that I can feel effective…  This in the middle of the Christmas production and my other duties taking care of the IT needs have been overwhelming.
So that’s it… add in the usual family commitments for Christmas and New Years, a few days of illness, and you end up with some pretty sparse blog postings.  However, I am seeing the light at the end of the tunnel on most of these things, so hopefully I’ll have more to blog about real soon.

Out of the darkness

If anyone has noticed that the blog activity has decreased, they’re right… It’s not because I’m abandoning the concept, It’s really just a concurrence of a few things …

1) I stopped doing the TechRepublic Stategies that Scale newsletter.  That was four postings a month (one a week.)  I really enjoyed writing the content for the newsletter but it wasn’t aligned to the things I was doing on a day-to-day basis so I had to let it go.

2) I’m transitioning between series at  Whenever I transition between series it disrupts the writing schedule.  We should be back on track this month but it means that I didn’t have the two posts per month I normally have announcing those articles.

3) I’ve been busy trying to figure out the eCommerce portion of the software development factory that I’m doing.  You’ve seen some announcements for betas…  I’ve got one issue to take care of in one of the products but otherwise the feedback has been good.  The net effect of which is I need to figure out how to start selling them.  I’ve taken a few wrong turns ( and the delay has caused me to decide that I want to build the new site on ASP.NET 2.0 which has turned out to be a giant gravity well which my time is falling into.

4) .NET 2.0 is really cool.  I’ve been playing with generics and how they can take typical problems and make them easier.  The obvious answer is collections.  However, I’m also very interested in taking the factory pattern and making it strongly typed and generic…  Unfortunately, I’ve decided that I’m starting from scratch so that means new database access code, new configuration management code, new collections code, and the new factory code … That’s meaning that it’s consuming a lot of time.

5) I can’t stop developing products.  It’s sort of like an addiction.  I see more needs than I can fill … I wrote a tool to manage web parts on any web part page in SharePoint (here’s a hint, almost everything is a web part page — including list pages).  It will allow you to add, delete, extract, and enumerate web parts.  (It’s done if anyone wants to play with it.)  I’m finishing a Url Administrator that allows you to change SharePoint List Fields which are of type URL.  The idea is that users sometimes use URLs in the portal that you wish they hadn’t — or you need to change.  This tool will go through the entire portal and organize all of the links for you.  It’s about 50% done.  I also have a tool which will go through and trim the versions in document libraries — more than a few clients have accidentally turned on versions in their document libraries and now aren’t sure how to get the versions trimmed.  That’s about 40% done…

6) I’ve been sleeping.  I try not to but occaisionally I’ve just got to.  My favorite catch phrase is “Sleep is optional.”  I’m being reeducated that it isn’t.

By the way, I’m looking for a mentee, protégé, coachee, who would be willing to work for a little bit of money and some good experience.  I need some help clearing some of my development tasks since I just can’t seem to get them all done.  If you’re interested drop me a line.

Requirement: Collaboration

The next time I see a requirements document which says they want “collaboration” my response is going to be to ask…

“Why do you want to cooperate treasonably with a foreign power?”

Maybe that will jar people into asking what they mean by collaboration.  (Asking what they mean by collaboration doesn’t seem to work in most cases.)

No Wake Before 10:00 AM

Every Parent’s Dream…

I saw a sign that every parent has dreamed of…

No Wake Before 10:00 AM

Maybe they weren’t talking about that kind of wake.

Recent Posts

Public Speaking