3 ms·
I think a better definition is: Has the term "{library_name} developer" been adopted as a title? "react developer": yes. "moment.js developer": no. "rails devel
by bdcravens 6y ago
I think a better definition is: Has the term "{library_name} developer" been adopted as a title? "react developer": yes. "moment.js developer": no. "rails developer": yes. "devise developer": no.
- zomglings 6y agoOho! I really like this! :) Very clever!
- CraftThatBlock 6y agoNode developer. Web developer. Doesn't really work fully.
- bdcravens 6y agosure, that's why I was limiting it to {library_name}, though arguably node could be that.
- woutr_be 6y agoI kind of disagree with that, a lot of companies will use terms like "react developer" or "react native developer" because they're looking for specific skill sets, only targeting those skills by explicitly naming their role after it. A lot of bigger companies also usually higher through recruiters, who usually are non-technical and will make up those names. In reality, you'll most likely be a software engineer specialised in react development.
- hinkley 6y agoI guess I never really considered jQuery a framework, and yet that was an adjective.
- bdcravens 6y agoI did, simply because it became the defacto interaction layer, with its ecosystem of first- and third-party plugins. Perhaps a plugin ecosystem is another defining characteristic: I think the "all batteries included" property most people associate with frameworks seems a bit limiting.