Why Computaphile
Nearly every project I have done started with a chance conversation.
Most of my software projects began by accident. Someone I happened to meet mentioned a job that was taking far too long, or a form that had to be filled in by hand, and asked whether anything could be done about it.
Over the years that has included:
- Safety documents that had to be printed, signed and accounted for
- Wage calculations covering absences, cover and split cover
- Shift rotas
- Organising bookings and enquiries
- A web site for a charity that had none
Start small, then let the job teach you
Each one started as a basic prototype, and grew into a complete application that genuinely saves time. This is still how I prefer to work.
-
1
Build the smallest useful thing
Something small enough to put in front of the person who asked, so they can tell me what is wrong with it. Nobody can review a document properly; everybody can review a thing that runs.
-
2
Put it to work
Used in anger, on the real job, with the real awkward cases. That is where the requirements actually come from.
-
3
Extend it, and extend it again
A round at a time, in the order the work demands rather than the order a specification imagined.
-
4
Leave it running
Eventually it is a complete app that improves efficiency and needs very little from anybody. Some of mine have been running for twenty years.
Recognise the problem?
If something in your week is eating hours that it should not, that is exactly the sort of thing I like to take apart.