Publication Date: 11/17/2009 2:20:16 PM
My new thermostat has a myriad of features, including a sensor that will tell me the outside temperature. The thermostat doesn’t use this information – it just reports it, with lots of information about the climate inside my house (temperature, humidity, etc.)
One problem: the outside sensor is in a spot that gets the full morning sun. This means that this morning, when the temperature was actually 30 degrees, my thermostat said it was 61. I have seen the reported outside temperature be off by more than 40 degrees!
There really isn’t a good alternative location for the sensor. They could build a little shade around the sensor so that it wouldn’t be in direct sunlight, but that is overkill and would mar the look of my siding.
Okay, but what does this have to do with software? There is a point. I promise.
I’m sure the person who designed this thermostat thought providing the outside temperature would be really great. But features add complexity. And features have to be supported.
In this case, there were extra installation steps for the installer. And then there is the explanation for why it will sometimes be wrong. And the additional work if I decided I wanted them to build a sun visor for the sensor.
This is true with software too. Every feature you add to your application increases not just development time, but testing time, learning and training time, documentation time. So the decision to add a new feature should be weighed carefully. Is it worth it?
Think like a geek
Jacki Hollywood Brown
on 18 Nov
Mark W. Schumann
on 20 Nov
Your URL (optional):
Type the code shown
Top 5 Programmers to Avoid
What everyone should know about bugs
How to tell if an estimate sucks
The Secret to Building a Crappy User Interface
The Problem with Selecting the Lowest Bidder
5 Ways to Control Software Development Costs
Avonelle is an incredibly talented software developer. She works fast, is economical, and offers great insights into the project at hand. She is also not afraid to speak up when she has concerns about a decision or approach. We’ve utilized her talents on many of our software development projects over the years.
Carrie Rocha, Chief Operating Officer @ HousingLink
Copyright © 2013 Avonelle Lovhaug. All Rights Reserved.
Sitefinity ASP.NET CMS