3 ms·
> Some of the best folks I've hired or worked with had no experience with the framework/language we ended up using. Knowing fundamentals is far more important.
by wwweston 11y ago
> Some of the best folks I've hired or worked with had no experience with the framework/language we ended up using. Knowing fundamentals is far more important.
This is what we want to be true.
It's not how 90+% of job listings are written, and I'm not sure it's how we hire.
Even if we addressed that problem, it'd still only be true at a close approximation: once a framework/lib/language becomes leaky enough, or has enough of a mismatch between its natural invocation and the problem domain, or carries enough of a culture of The Right Way To Do It™, then it's true that experience with the tool matters... as long as the org is more invested in the tool than a solution that doesn't have those problems, knowing the tool's foibles and practices remains important.
- nostrademons 11y agoCompanies have a wide variety of hiring practices. By making yourself bad at one hiring procedure but good at another, you'll select for the companies that are selecting for developers like you. Getting a job is not a numbers game unless you just want any old job and really hate jobsearching. I've found that making myself unappealing to the organizations that I wouldn't actually want to work for has paid off significantly in both financial and job satisfaction terms.