2 ms·
I’ve always developed this way and I’m surprised how often other developers will spend all sorts of time on tertiary tasks or will compromise the stability of t
by CoolGuySteve 8y ago
I’ve always developed this way and I’m surprised how often other developers will spend all sorts of time on tertiary tasks or will compromise the stability of the critical path for the sake of some abstraction.
Make it work, make it work correctly, expand from there. But it must always work.
One example I saw recently of this done wrong is Duo Lingo. That app’s subscription’s main feature is the ability to do lessons offline. The thing is, it almost never works and it’s been buggy for years now because the app refuses to cache enough data and has poor syncing support.
How can you fuck up your principal revenue stream like that? It should be the critical path.
- hef19898 8y agoSame goes for process development. I have seen tons of people bloating processes to cover tha last imaginable exception and forgetting the core function. In the end the exceptions worked, the standard didn't.