4 ms·

I really like the idea of approaching rapid development like writing an essay or a blog the first time. Just getting all the words out on the paper goes a long

• blackflame7000 10y ago
  I understand your mindset, but sometimes a little bit of planning upfront can save so much time in refactoring. I'm not sure code is analogous to writing save for maybe a choose your own ending type novel. An Essay is essentially a sequential flow of ideas where as a program is more like a tree. Perhaps what you are referring to is rapidly developing the nodes(classes) of that tree without concerning yourself to much with the connective branches between classes. If that's the case then I can see the benefit.
  • Drdrdrq 10y ago
    From purely technical viewpoint that is correct and engineer in me agrees with you 100%. However: if you look at the bigger picture you will notice that the feature list is not known in advance. Which means the nice abstraction you made are probably unsuitable and will make repurposing software more difficult, not less. Because nobody knows what the end product will look like, so it pays to ship fast, iterate on product design and refactor / rewrite later. But I know what you are saying, I have struggles with that inner engineer daily and he just won't shut up. :)