2 ms·
The problem with that approach is that your product becomes cluttered and looks old as years go by with only small enchantments and fixes. Here is a middle grou
by aytekin 9y ago
The problem with that approach is that your product becomes cluttered and looks old as years go by with only small enchantments and fixes. Here is a middle ground: continuous improvement with yearly strategic planning.
https://medium.com/swlh/how-we-develop-products-for-3-2m-users-f5ec8895ee47 https://medium.com/swlh/how-we-develop-products-for-3-2m-use...
- jpfed 9y ago>The problem with that approach is that your product becomes cluttered and looks old as years go by with only small enchantments and fixes That's why you have to throw down a Tranquility/Jokulhaups combo every few years; get a fresh start.
- tatersolid 9y agoTotally untrue, we actually rebuilt several complex services this way, and did a front-end refresh as well. So long as you prioritize the starting “enhancements” of a theme or epic it can work. These early tasks usually produce architecture diagrams, API signatures, wire frames, or demo code.
- OnlyRepliesToBS 9y agoLooks old? It's called MATURE SOFTWARE. The BEST kind of code is the kind that IS JUST FINE by itself. Today it's more about looking busy.