3 ms·
Probably architecting and choosing between options, though it's not all wasted. Most of the stuff I do can probably be best done by doing an ugly first implemen
by _delirium 16y ago
Probably architecting and choosing between options, though it's not all wasted. Most of the stuff I do can probably be best done by doing an ugly first implementation, throwing it away and replacing it with a better one, and then abstracting out some nice modules and interfaces, and iterating from there. But my instinct is to analyze the problem up front, decide what the right interfaces are, which the right third-party libraries (or even languages) are, and before you know it, I've spent a whole day reading about Clojure's concurrency primitives, or pros and cons of different OO patterns, or comparisons of Library X and similar-sounding Library Y. The worst is when the available information isn't that good, so all I've gotten out of my hours of reading is, "huh, libraries X and Y sound pretty similar, and I still don't really know which is better for my purposes; I'll just have to pick one and see".
It does occasionally lead to an epiphany of the "aha, my problem is exactly [this]!" variety, so sometimes it works.