Timeline for What are your initial three steps when you are first presented with a software problem?
Current License: CC BY-SA 2.5
4 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Oct 26, 2010 at 0:00 | comment | added | Inaimathi | +1 @JBRWilkinson In practice, even if you spend copious amounts of time thinking what needs to be done before delivering, the client will take one look and want something different. Even if what you built was precisely what they asked for in every conceivable way, and you got sign-offs and clarified thoroughly. Some mix of incremental development and/or fantastic sales + legal departments is the only solution I've seen. | |
| Oct 19, 2010 at 17:45 | comment | added | John | @JBRWilkinson: Well I guess step 1 would be more like me writing my preconceived template of what I want it to look like. Setting up a basic framework before I delve into it in-depth. | |
| Oct 19, 2010 at 8:39 | comment | added | JBRWilkinson | You'd write code before deciding what needs to be done? Huh? Surely (2) before (1) ? | |
| Oct 19, 2010 at 0:51 | history | answered | John | CC BY-SA 2.5 |