2 ms·
The deeper I get into my career, the harder my bad decisions have bit me later. For JS-in-the-browser at least, I feel like it’s less about which framework/par
by graypegg 2y ago
The deeper I get into my career, the harder my bad decisions have bit me later.
For JS-in-the-browser at least, I feel like it’s less about which framework/paradigm you pick today, but more about how your choices will limit your options in the future. If you could predict the future, you’d just choose the framework with the longest maintained life, but you can’t, so just focus on maximizing abstractions in the framework built on the slow-changing parts of the web (HTML/CSS, browser APIs) and try to consider how it would integrate as the “legacy” application you’ll be bemoaning only 5-7 years from now.
Some of the most successful companies I’ve heard about have legacy applications. Aiming to make the perfect choice for all future problems up front seems like the wrong choice IF it prevents you from changing your choice without tearing everything down first.