4 ms·
> It's usually not "how to get a simple task done with React" – many engineers can get there very quickly – but rather having an understanding of best-practices
by AFNobody 9y ago
> It's usually not "how to get a simple task done with React" – many engineers can get there very quickly – but rather having an understanding of best-practices in terms of architecting your application.
Find me a Web Developer than can perform a sysadmin role on production sites, building out a CRM integration on some bizarre platform with its own programming language, work on improving an ERP, and the integration between them. Oh, and you also need to know React and some standard MVC stack like RoR.
No?
---
Now, you might think that is a joke or absurd. It is not. It is also as relevant an expectation as asking if they know React.
Your point of view screams silo'd front end developer.
- mgkimsal 9y agoI can do all that, but no one would want to pay what I'd charge for all that.
- PeterisP 9y agoIf any large-ish company hired such a candidate, it would still likely use them in a pure front end development role, because administration of production sites would be handled by dedicated people (sometimes by necessity - e.g. PCI DSS and other security standards like to ensure a strong separation between development and production teams); CRM/ERP would be handled in a different team, etc. Specialization is a thing, if your team isn't tiny, you'll have different functions handled by different people.
- AFNobody 9y agoPeople keep telling me that but I've worked in S&P 500 companies, startups, etc. Somehow, somehow it never seems to be true if you are doing anything close to "architecting" anything.