2/ If you make the wrong design choice, it can cascade quickly & cause long term damage (e.g.: trust wasn’t a consideration in early Internet protocols). It can take years of trials & errors to develop good insights, no matter how smart you are.
-
-
Show this thread
-
3/ One example I've seen personally: junior devs tend to overuse things like Inheritance. It’s very natural to think “is-a” architecture makes sense.
Show this thread -
4/ Only after you’ve seen enough tech debt & done enough refactoring
you appreciate the importance of flexible design, aka “has-a” architecture. Inheritance should be used very carefully & selectively.Show this thread -
5/ Some other areas where experience matters are things like caching, networking, distributed system, security. These are really hard problems.
Show this thread -
6/ A corollary of this is that any cryptocurrency that doesn't have depth & experience behind its dev team, that usually is a bad sign.
Show this thread
End of conversation
New conversation -
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.
