3 ms·
Also known as the Feynman Algorithm. I've done that quite a few times too, and found it to be faster than trying to "design as you go" and having to constantly
by userbinator 9y ago
Also known as the Feynman Algorithm.
I've done that quite a few times too, and found it to be faster than trying to "design as you go" and having to constantly debug and make incremental changes to fix things (which also tend to have the effect of making the code messier.) If you think everything through and then write the code, the only bugs tend to be minor, spelling-related and such, but otherwise the code usually "works the first time".
- gonzo41 9y agoYeah i do this mostly, but it's hard to be agile when all I want to do is ponder a problem for a sprint. I also find writing a plan helpful if only enumerate the issues at hand. It always changes but its good to start with. I find generally this approach leads to less production crippling errors.
- AnimalMuppet 9y agoExtreme Programming has this idea of a "spike". It's throwaway code that you write just to figure out how to do something. (The name comes from trying to "nail something down", I think.) That's not quite just thinking for a sprint, but it's in the same direction.