MVP stands for (in this article) Minimum Viable Product. It’s not an Agile concept.  It’s not even a software-specific concept, though it’s certainly easier to do with software, since upgrading software is usually easier than upgrading hardware.  The concept is simple: Instead of building every feature under the sun into your product then releasing it, build the least you think people will buy and release that, following up with more feature-rich versions.  There are several good reasons to do this.Continue reading


Since I’m in Boston, we have a lot of snow to deal with this winter.  The other day I was clearing snow off my roof with a roof rake, and after about an hour for some reason it started pulling to the left when I pulled straight down.  I started to compensate by pulling the roof rake more to the right to compensate, but that didn’t really help much.  After finally getting frustrated enough to pull the roof rake down and look at it, I saw that one of the support brackets was no longer screwed to the rake, so the blade was unsupported on that side.  That’s why the rake was pulling to the left.  Had I looked at the rake as soon as I noticed the problem, I would have saved a lot of frustration, and possible permanent damage to the roof rake.  I fee we do the same thing with our software tools a lot.

Very often I’ve seen software where the usual reaction to compilation warnings is to tell the compiler to ignore them.  There are times when this is appropriate.  My favorite example of this is with Java Generics, where it’s very hard to get around some of the warnings for things that you and I know are perfectly safe.  Most of the time, though, compiler warnings are indicating a moderate to serious problem, or at least an area where the program might not be doing what you think it is.  Eliminating those warnings is an excellent collaborative activity, because we all have experience with different software issues.

So the next time you feel tempted to “ignore the Check Engine” light, spend some time finding out if there’s a more elegant solution than putting tape over it.


As a Software Engineer and as a geek, I face many tempations.  One of them is “I can add this really cool feature while I’m in the code, and it will take hardly any extra time.  It won’t impact any of my other work at all”.  There are some very good reasons why you shouldn’t do it though, and why it’s an Agile anti-pattern.Continue reading


When someone, especially new software developers or those still in college, asks me whether they should learn Java or C#/.NET, my normal answer is something like “They both do about the same thing, but Java will run on almost anything, and almost all the development tools are free.  With C#/.NET you could pay hundreds for Visual Studio, and the programs will only run under Windows.

Microsoft has a long history seeing open source as the enemy, but has never had a problem stealing ideas from it. They even use marketing jargon that is directly opposite of reality.  My favorite case of this is Microsoft Windows Services for UNIX, which is actually UNIX-like utilities you install on a Windows computer to give it UNIX-like functionality, not something you add to a UNIX box to help it communicate with Windows.  In the past Microsoft has even called Linux a cancer.  These days they’re singing a different tune, one that goes “We love open source“.  We know what the motivation is.  In the real world, business computing environments are of mixed architectures and operating systems.  Everything needs to interoperate.  They’re not going to dominate the server world like they do the desktop.  But you know what?  I don’t even mind that they don’t mean it as long as they act like they do.  And they are.

Microsoft is opening up major parts of the .NET codebase to open source.  They’re doing so under the MIT license, not a GNU license, and that makes sense.  They’ve made major contributions to Linux in the past decade.  There’s also now a community edition of Visual Studio so you can use it for learning and some projects for free, which is long overdue for them.

I’m a Linux lover, not a Microsoft hater.  Any steps they take in the right direction are OK by me!


There are a lot of technology options out there.  There are even a lot of free/open source technologies out there.  So much so, that it’s tempting to install too much of it.  Having too much technology can be just as bad as having too little, and “free” can become pretty costly.  Obviously I’m not knocking free/open source, but the misapplication of it.

First and foremost, the more software/hardware you have, the more likely it is that some of it will have a bug.  That’s just law of averages coupled with the fact that no significant software project is really bug-free.

Then there’s the maintenance effort.  The more technology you have, the more effort needs to go into care and feeding of it.  Also the more you have to learn about.

Lastly, just how Agile teaches us to delay decision-making and development to as late as possible, because that’s the point where we know the most about what’s needed, the more technology you put in place before you need it, the harder you make it to implement what you really need when you do.

Continue reading


I have been an early adopter for many electronic devices, especially mobile ones. I’ve had the dream of walking around with some sort of computing device, ideally connected to the Internet, much longer than it’s been practical.  I went through the HP100LX (which I could hook up to my Motorola Startac phone or my 300 baud modem), the Sharp Zaurus SL-5500 (which ran Linux), and the Psion 5MX.  Then some Palm PDAs, etc.  Unfortunately, the PDA market is pretty much dead.  I really wish I knew why, as it was years between when the PDA market vanished (at least here in the US) and when smartphones became capable of taking their place.

My first smartphone was a Windows Mobile 6.0 phone (bought months before Microsoft declared Windows Mobile 6.x an utter dead end), and eventually an iPhone.  But not the first iPhone.  Or even the second iPhone.  Why?  Because, as groundbreaking and powerful as they were, my research determined they were missing certain key features that I needed to do what I want, and being a relatively closed and restricted environment, those features were not going to be added on by someone else.  I did my research, and said “Not soup yet”.  How do you release a device you say surpasses anything else without cut/copy/paste??!?!?  I am very much NOT an Apple Fanboy, but why, being a Linux Fanboy, would I not go with an Android phone?  because (1) At least at the time, you couldn’t back up or sync any data with an Android phone without surrendering all your contacts, schedule, etc with Google, which is an unacceptable privacy violation to me, and (2) AT&T had modified the phones to be even more locked down than the iPhone!!!  But I wold not have known that if I just simply said “The Linux-based phone must be more open, so let me get that one”.

When the Kindle Fire was announced, I started thinking about getting that device, or something like it (7″ form factor Android device around $200 with a high quality display).  Days later the Barnes and Noble Nook Tablet was announce to be available for sale a week after the Kindle Fire, and I quickly narrowed down my choices to these two.  But the rumors and predicted specs on review sites differed enough I knew I had to wait until they were available and I could play with them.  I ended up developing a detailed, objective comparison between them, and the Nook Tablet won handily (for me. YMMV).  I got active in the Nook Tablet “hacking” community, and even started working on a wiki site on it. My research found that the boot loader was heavily locked down, and while there’s a lot of hacks to load other software and markets and customizations for it, it’s unlikely that a completely new ROM would be loaded on it any time soon.  I was OK with that, because while I wanted to do much more than originally intended with the device, I still wanted it to function as an ereader, too,

I noticed, long after the word had spread that you couldn’t [yet] replace the ROM as you could in its predecessor, that people were buying them and discovering this after the fact, and returning them.  These people had bought this device for $250 or more hoping to load the latest version of AndroidOS on it, use bluetooth keyboards, hook up external hard drives to it, and Skype their friends with it, without spending half an hour finding out whether any of this is possible (none of it is yet, though Ice Cream Sandwich is close)!

This leads to unhappy geeks.  Geeks and hackers, as a group, tend to expect the world to work they way they want it to, or at least be configurable to.  Only big corporations aren’t always on board with this.  In the case of the Nook Tablet, B&N had to lock the tablet down more than its predecessor in order for Netflix to allow streaming on it.  After the security vulnerabilities came out that allowed us to gain root access to the Nook Tablet and load software from wherever we wanted on it, B&N pushed an update to the software that closed those security holes, and that update got installed on Tablets with no warning, and certainly without consent.  There was an endless barrage of flame wars complaining that B&N should not have done that, and “how dare they”.  I would calmly point out each time that B&N was operating in their own best interests (protecting their relationship with Netflix and other companies), and it’s silly and unrealistic to expect B&N to act against their own best interest to enable a small group of people who will never buy books, movies, or apps from B&N to have their fun, any more that one would expect Apple to allow Adobe Flash on the iPhone or Ford to allow you to connect your computer to the diagnostic interface of their cars with a simple USB plug.

So here’s my message: When you’re planning on buying some sort of complicated and/or expensive item:

  1. Make sure you’ve identified exactly what you want to do with it (establish acceptance criteria).  This not only helps you with your research, and help determine when you’re done with it, but it can prevent you from falsely claiming you’ve found “the perfect solution” if you really haven’t.  It also helps convey to others what you’re looking for.  Be honest with yourself.
  2. Make sure you’ve made a reasonable effort to identify all possible items that could meet your needs.  “Premature optimization and/or filtering” can lead to excessive narrowing of the result set.
  3. Make sure you look at both the good and bad features of each item, identifying any deal-breakers.
  4. If you absolutely need a feature, and the device doesn’t have it yet, don’t assume that it will be added in the near future, or ever.  Even barring external influences like regulations and partnerships, their idea of the future of the device may be very different than your own.
  5. If you can afford to wait even a week later, you will benefit from the experience of the others who were not so thorough.  Learning from other peoples’ mistakes is much cheaper than learning from your own.  Learning from other peoples’ successes can save you hour of research.
  6. If you can’t find evidence either way whether the device can do what you want it to or not, don’t be afraid to ask.  And ideally, spread the new knowledge.