Publication Date: 2/15/2010 6:38:17 AM
Whenever I’ve heard people talk about the importance of a single point of contact for communication between the developer and the “customer”, I’ve thought this was primarily to protect team members from unnecessary emails and meetings. But what I’ve come to realize is how important this is to project health generally, for a couple of reasons:
If only one person is giving the programmer feedback, they are less likely to get conflicting messages about how things should work.
Less communication about the communication
As a programmer on the outside of an organization, I often can’t tell who will ...
Publication Date: 1/18/2010 9:06:43 PM
Most programmers who have been around a few years can tell you horror stories about a software project they worked on. The stories are varied, but most of them involve an “unreasonable” customer who kept changing their minds, and the project suffered from lots of rework and frustration, or perhaps didn’t even get finished. (Even I have a story like that.)
Which is why programmers are often surprised to learn that I don’t charge by the hour. They’ll ask, “Aren’t you worried that the customer will change their mind repeatedly and you’ll lose money?”
Most customers aren’t ...
Publication Date: 1/10/2010 8:51:36 AM
One of the more frustrating aspects of being a programmer is that sometimes users encounter problems you never hear about. It isn’t anyone’s fault – I don’t always notify people when the software I use generates an error either. It takes time and effort, and I often think “they probably already know”.
But honestly, we don’t always know about the problems users encounter. Especially on smaller software projects with a limited number of developers and testers, we’re unlikely to test every single scenario. So the problem a user discovers may not be anything we tested for or have seen ourselves.......
Publication Date: 12/8/2009 6:33:17 AM
Ask the programmer is a feature designed to answer questions from non-geeks about hiring and working with programmers. If you have a question, please email me at email@example.com.
Question: Why doesn’t your custom software contract grant my company ownership rights for the code. I’m paying for the software, shouldn’t I be the owner?
Answer: To start out, we need to have a common understanding of what is included in custom software. Most custom software is made up of several different things:
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 ...
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 has been a pleasure to work with. Working with someone that you know will always deliver is tremendous.
Mark McNamee @ Renewal by Andersen
Copyright © 2013 Avonelle Lovhaug. All Rights Reserved.
Sitefinity ASP.NET CMS