4 ms·
> “Product-first” engineers are obsessed with using code to solve a user problem and they see code as just a means to an end. > “Code-first” engineers are obse
by ramoz 5y ago
> “Product-first” engineers are obsessed with using code to solve a user problem and they see code as just a means to an end.
> “Code-first” engineers are obsessed with the abstractions, architecture, tools and libraries in the code. Elegant code is the end.
Eh, from my experience it's quite the opposite, if we're talking frontend vs backend. Frontend is a complete abstraction these days, all about the tools & libraries, a bit less focused on sound architecture, and usually the only thing elegant is the cursive font JS devs use in VSCode.
- lhorie 5y agoMy understanding of the article is that product-first doesn't equal frontend, but rather that frontend-vs-backend and product-vs-infra are two different ways to categorize engineers, and that looking at roles from the latter's lenses may help in placing candidates in roles that fit their preferences better. This is a good insight, especially because in big companies, attrition seems to be a constant HR issue. In my experience though, the problem is that the premise of this article presupposes a large enough, diverse enough engineering organization. For smaller shops, there may not be such a thing as a frontend architecture oriented role, or there may not be upper management support for infra oriented roles, etc.