8 ms·
Can't disagree with any of those really. I guess it's really hard to draw out general conclusions about these sort of things when the specifics really make a di
by IshKebab 4y ago
Can't disagree with any of those really. I guess it's really hard to draw out general conclusions about these sort of things when the specifics really make a difference. You can pretty much say "spend your time wisely" which is not very actionable.
For instance on your last point - I've heard that used to argue against any new technology even if it solves real problems. Rust, Bazel, React, Typescript, etc.
I would go so far as to say some of these general principles can be harmful because they are mostly used as a lazy way to defend bad decisions. E.g. "premature optimisation" is more often used to justify ignoring performance entirely than it is to stop people writing things in assembly or whatever.
- bluefirebrand 4y agoPremature optimization is much more useful as a deterrent for stuff like building complex data structures and processes to speed up looping through like 100 items. "But it might be a million items later!" Yeah, or the company might pivot before we ever go live with this feature. Just slap a for-loop in there and get on with your day.