From a maintenance perspective, the key to system longevity is to decouple interfaces and implementations. From a relevance perspective, the key to system longevity is to achieve a critical ecosystem mass.
Show this thread
First point: over time, you need to be able to change your internals without changing your public APIs (which users & ecosystem libraries build on). If you can't do that, you'll be forced to maintain near-static internals (a maintenance nightmare) or else invalidate your ecosytem
-
-
Second point: no particular feature or performance advantage of a system can last very long. But ecosystem gravity is extremely tough to replicate, and is the single most impactful element when it comes to *reducing time to solution* for end users (which is the end goal).
Show this thread -
Who would use Windows without the apps? Who would use Python without the libraries? It's not the features. It's the ecosystem.
Show this thread
End of conversation
New conversation -
-
-
How the public accesses your database remains static but the work happening within your database to feed those endpoints can change?
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
It's 2am and I read it thinking it's life advice written in nerdy language. Works in mental health/being yourself context. But is kinda sad. I shouldn't post to twitter at 2am
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.