4 ms·
Sure. Only that's entirely not what the article says. It says not to focus on details _too early_. Because while the entire team may (or may not) agree on the g
by krautsourced 14y ago
Sure. Only that's entirely not what the article says. It says not to focus on details _too early_. Because while the entire team may (or may not) agree on the general idea, getting into the details at the same time will take _much_ longer, with very little gain (since that early in the project it may not even be sure if that detail will even be relevant later on). Get the rough ideas sorted out first. Then chip down, iteration by iteration. Finally, get to the details (and then it's time to pay attention to those).
- locacorten 14y agoOn surface, you're right. However, I've never encountered a person who pays attention to details and can switch this on or off, depending at which stage the project is in. You either care about details (and you can't help yourself), or you don't. When you are good but don't pay attention to details you end up with things like ... the Facebook website. You make a million bucks by some random chance and then you start writing crap articles like this one. And then all the cool under-30 kids start worshipping you.
- thisone 14y agoGive someone a project where there's not enough time to nail down every detail and complete the project. Either they fail by not producing a working product, they learn to prioritize, they burn themselves out and get it done to their standard, or they quit because they can't accept that sometimes deadlines matter more than details.