Tag archive for “Development Process”
“What made oil paint so exciting, when it first became popular in the fifteenth century, was that you could make the finished work from the prototype. You could make a preliminary drawing if you wanted to, but you weren’t held to it; you could work out all the details, and even make major changes as you finished the painting. You can do this with software too. A prototype doesn’t have to be just a model; you can refine it into the finished product. [...] It’s good for morale.”
“Don’t keep “trying” solutions until you find one that works. Take the time to find the correct solution.”
“Cringley’s Second Law: Ease of use with equivalent performance varies with the square root of the cost of development. That means that to design a computer that’s ten times easier to use would cost 100 times as much.”
“Agile methods derive much of their agility by relying on the tacit knowledge embodied in the team, rather than writing the knowledge down in plans.”
“With proper design, the features come cheaply. This approach is arduous, but continues to succeed.”
“The job of the average manager requires a shift in focus every few minutes. The job of the average software developer requires that the developer not shift focus more often than every few hours.”
“A brute force solution that works is better than an elegant solution that doesn’t work.”
“The software isn’t finished until the last user is dead.”
“There is an old saying with software that three years from now, no one will remember if you shipped an awesome software release a few months late. What customers will still remember three years from now is if you shipped a software release that wasn’t ready a few months too soon. It takes multiple product releases to change people’s quality perception about one bad release.”