3 ms·
this is easier said than done, but the key to avoiding analysis paralysis is to worry about building the right abstractions and only that. if the software is a
by rguzman 14y ago
this is easier said than done, but the key to avoiding analysis paralysis is to worry about building the right abstractions and only that. if the software is abstracted well -- ie it correctly represents the underlying problem at an adequate resolution -- then it becomes easy to say YAGNI in the short run with the confidence that refactoring or adding functionality will be straight forward later.
- Morg 14y agonot really. because you can over analyze what the right abstractions can be. it's only a matter of how abstract you want it to be, believe me. Analysis Paralysis is inevitable as long as you want to write the RIGHT thing. As soon as you accept "good enough, we'll upgrade later if necessary", you start moving towards the right thing. Anything that says perfect, adequate, right, correct, etc. is wrong and leads to the dark side.