3 ms·
You're not wrong, but I don't think anyone is saying you shouldn't use appropriate data structures. To me the advice means don't belabor the choice of data str
by ses1984 8y ago
You're not wrong, but I don't think anyone is saying you shouldn't use appropriate data structures.
To me the advice means don't belabor the choice of data structure of its not obvious to you.
If you're writing a quad nested for loop to solve a problem, don't get distracted trying to refractor all the work leading up to that wart... Just get it down first.
Get a passing test first then optimize later if the code is a bottleneck.
- TeMPOraL 8y ago> Get a passing test first then optimize later if the code is a bottleneck. In that case, totally get that test passing and then maybe add few more tests around that solution - so that when I come to the project half a year later, and see the application consing like crazy because you used lists instead of arrays, and this now powers half of the business logic, I can tear this up and fix the data structure with confidence I won't break things badly. (Totally not a real case I had.)