Archive for January, 2010
Thursday, January 21st, 2010
Scenario: A customer has a problem with your software. His questions makes you think and you get an idea for a feature improvement. A good one! Act on it.
Plan it
Code it
Test it
Commit it
Deploy it
Nothing out of the ordinary, it seems. The seemingly new thing about continuous deployment is that we ...
Posted in process, teamwork | 2 Comments »
Saturday, January 16th, 2010
Defining what great software is, is not a complex endeavor. I prefer to boil it down into two distinct characteristics.
a) Ease of Use
The software solution walks you gently through the process of solving your problems as intended. No distractions, no unnecessary decisions to make, no confusions, always heading towards the ...
Posted in process, software | No Comments »
Friday, January 8th, 2010
How you design your team has a great deal to say for the speed and quality of the resulting work the team will do.
Speed
The ultimate ideal for speed is a one-man show.
There's this one guy doing everything in the project. He is competent in engineering practices such as software design, ...
Posted in teamwork | 1 Comment »
Sunday, January 3rd, 2010
There are three prominent problems in the software industry that bothers me in particular at the moment. Being a part of that industry, I feel somewhat responsible to help shed some light on these problems. I list each problem below, with a proposed solution outlined.
Problem 1. Foot-in-the-door Software
The recipe for ...
Posted in software | 3 Comments »
