making time estimates
Posted by noah on May 22, 2008
when i switched to strictly dev work, i thought that i would have a hard time with giving and meeting work estimates because i’m a slow coder. turned out that i’m not that bad. i think i just have to double my initial idea of what it would take because i don’t take into account everything i need to do.
for next time:
- get a feature list. this last time, my boss kept adding on stuff. not that he expected me to be on time with the extra stuff, but it still helps when designing and planning
- prototyping, proof of concept… (can i read the bytestream records off the socket connection?)
- is there a client ui?
- working with unfamiliar code?
- functionality testing
- perf
- refactor, review code
- other work being done in parallel
