4 ms·
Thanks for the link, wallflower. I forgot about that. (Buy the book anyway. You just don't know which chapter might change your life.) This pretty much sums
by edw519 18y ago
Thanks for the link, wallflower. I forgot about that. (Buy the book anyway. You just don't know which chapter might change your life.)
This pretty much sums it up for me:
"When you design with very few parts, everything is so clean and orderly you can understand it more deeply in your head, and that causes you to have fewer bugs. You live and sleep with every little detail of the product."
- 10ren 18y agoI was going to object to your "finger on the pulse of every detail of their project", because as complexity increases, it eventually becomes overwhelming and too difficult to understand, and you have to construct intermediate representations to handle the complexity - that is, a form of modularity, not for coding it, but just for understanding it. But then I saw your quote here, about the need to understand it, and the having very few parts makes that possible, by limiting the complexity.
- edw519 18y agoHe says it far better than I. Hell, he does everything far better than I, even dancing. (Does he drink beer or play foosball?)