3 ms·
YAGNI. This is not so much as a force multiplier but as greasing the wheels, and I see it all the time Shipping and revenue should be your goal. Sure, aim for
by raverbashing 6y ago
YAGNI. This is not so much as a force multiplier but as greasing the wheels, and I see it all the time
Shipping and revenue should be your goal. Sure, aim for a polished product, but don't waste time with things that don't further your goal (unless it's a security/correctness/legal issue, sure)
- You don't need to rewrite your frontend in the latest .js library just because. Ship first, think about rewriting later
- You don't need to apply those 5% micro-optimizations if your site is working fine (at least not before shipping)
- You don't need your resources in a global redundant CDN right off the bat. Use existing CDNs (for .js for example)
- The thing that will break is not how you initially thought it would go. Avoid premature optimization unless it's really obvious (example: front page optimizations).
You might not even need code at first. MVP your thing.
- davnicwil 6y agoYAGNI is such a powerful philosophy that I think within reason you should look at it as a hypothesis to disprove on every new thing that you work on. It's really difficult advice to follow because, very often, the thing you don't need is actually quite fun to work on. You start out wanting to work on it, so the hypothesis becomes flipped: "why shouldn't I build this", or, "If I can build this, I should". Focusing on the category of things that fall under 'optimizations', the key here is that the problems they solve are not the problems you have when you launch something, and you will only have them at all if your thing is a significant success. They're nice problems to have. I wrote a short blog post on this theme recently: https://davnicwil.com/if-its-a-nice-problem-to-have-dont-solve-it-now/ https://davnicwil.com/if-its-a-nice-problem-to-have-dont-sol...