Publication Date: 10/5/2009 6:56:33 AM
Software estimates can be tricky. One challenge is remembering what to include. When people put together their estimates, they usually focus on the features but often forget some critical pieces that aren’t functionality specific.
You might think that as a customer you don’t need to concern yourself with this. To a degree you are correct. But if your software roll-out has dependencies that make hitting target dates critical, you’ll want to feel confident that the estimates are accurate. Also, some developers who charge on an hourly basis can low-ball projects by providing estimates that exclude these tasks. It will be ...
Publication Date: 9/25/2009 6:19:44 AM
Unless you are a programmer, you probably don’t read Joel on Software since, well, he writes about software development. It is too bad, because he actually writes about the business of software development, and not complicated coding techniques.
This week he wrote about The Duct Tape Programmer. HIs post describes a type of programmer who isn’t fascinated by the most cool, complicated programming solution, and instead focuses on building applications and shipping software. He compares this programmer to architecture astronauts who have really great ideas about building software, but their ideas require people smarter than most of us.
I think ...
Publication Date: 9/17/2009 7:04:58 AM
One reason why I am an advocate for fixed-fee pricing over hourly pricing is that I dislike the notion that the customer should be penalized if I make a mistake. I’m of the opinion that the customer should be protected from my boo-boos as much as possible.
There are a few kinds of mistakes that can occur on a software project. One kind of mistake is when the programmer creates a poor estimate of the required effort. This is a very common because few programmers are good at software estimation.
Some who charge hourly will not penalize the customer in ...
Publication Date: 9/15/2009 11:21:37 AM
I recently attended my nephew’s 5th birthday party. Observing him I realized that he and his guests could teach programmers a thing or two about software design:
Put yourself in someone else’s shoes
My nephew spends quite a bit of time playing with imaginary friends. And to him, they all have distinct personalities. (For example, one of his imaginary friends is a dead composer. Another is a penguin.)
Programmers often think too much like themselves when designing software. To design really great software, you need to be able to use your imagination, and put yourself in another person’s shoes.
Publication Date: 8/25/2009 3:44:33 PM
I was reminded today of the importance of being careful about the technology resources you hire. This article refers to a survey that suggests that more than 59% of employees who are fired, laid off or quit admit to stealing company data. Yikes! When you trust someone with your technology, you are giving them the ability to do severe damage to your business. Not only do you risk data loss or data theft, but there is also the potential of destruction of your reputation and brand.
Before you hire someone (internally or externally) to work on technology related activities for ...
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