2 ms·
There's writing code to handle every eventuality, and there's considering 3-4 places you MIGHT pivot and making sure you aren't making those pivots harder than
by CuriouslyC 2y ago
There's writing code to handle every eventuality, and there's considering 3-4 places you MIGHT pivot and making sure you aren't making those pivots harder than they need to be.
- blagie 2y agoThis is exactly what I try to do and what I've seen successful systems do. Laying out adjacent markets, potential pivots, likely product features, etc. is a weekend-long exercise. That can help define both where the architecture needs to be flexible, and just as importantly, *where it does not*. Over-engineering happens when you plan / architect for things which are unlikely to happen.