3 ms·
You've seen a couple of actual paradigm shifts, and the dozens of hype-cycles in between. You can tell the difference between the two: what's important and what
by typedef_struct 7y ago
You've seen a couple of actual paradigm shifts, and the dozens of hype-cycles in between. You can tell the difference between the two: what's important and what's not.
You've been up and down the stack enough to have a decent understanding of how things are implemented at the levels above and below the ones you work in. You can avoid the leaky abstractions in your stack and your abstractions don't leak on others.
- karmakaze 7y agoIANA FE-dev, but I don't think I've met many that fit this description. The closest I can think of is to settle on an acceptable/popular framework (e.g. React) and make it as pain free as possible (e.g. use TypeScript, clean component patterns). At the same time, current hype results in using React-Native for mobile which seems feasible but short-sighted to me. Maybe a better description is one who understands current trade-offs and makes pragmatic choices rather than seeking future payoffs.