Basically I was in the middle of implementing some new features when I went off on a tangent and started implementing something completely different. I was then stupid enough to attempt to launch these new smaller features, this resulted in a server with incomplete and partially untested code.
I was then running late for other commitments which lead to more pressure and more mistakes. The whole situation was a big sloppy mess however I think that I have rectified the situation now and definitely learnt some lessons along the way.
- Iterate fast, but not too fast. Make sure that things are solid and tested before they are released. A broken site is more offputting to users than a site missing a few cool features for a while.
- Instrument code to allow problems to be easily identified and fixed. I am in the process of making the system much more defensive and allowing it to email me as soon as any sort of problem is encountered (rather than having errors pop up in front of users in dialog boxes).
- Only work on one feature at a time. As soon as you start working on more than one thing at once, the uncertainty increases and it is unclear what feature is causing what problem. It makes it very difficult to roll back to a working system since you have interwoven changes.






0 comments:
Post a Comment