2 ms·
> “Product/Infra” maps neatly to the psychology of how engineers pick projects and their motivations for learning to code. Broadly speaking, there are 2 types o
by karmakaze 5y ago
> “Product/Infra” maps neatly to the psychology of how engineers pick projects and their motivations for learning to code. Broadly speaking, there are 2 types of engineers2:
> “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.
> Product-first engineers map to “Product engineering”—building, launching and maintaining features that solve user problems. They often love being in the same room as designers and product managers to learn about users, and they love finding technical opportunities that can improve the product.
So the main line of reasoning is that Frontend vs Backend can paint you in a place where you don't fit. Even combining the Front/Back and Product/Infrastructure axes I still can't describe what I like to do: Platform/API development. That is taking an understanding of the product/business domain, factoring them down, implementing them with a code-first mindset. It isn't exactly elegant code being the end, but having composable interfaces that separate conceptually. Add to that supporting and working with product developers who tend to be frontend/mobile either in-house or third party and sometimes other platform developers.
Early in your career, Frontend/Backend with a particular framework/language will sufficiently filter your options, as you specialize you will tend to be more specific. There are many axes as you specialize, for instance I work with several datastores in great depth. Oddly the frameworks/languages that were good filters hardly matter anymore as the solutions tend to be easily represented in any. I'm more than competent with frontend but my interests and concerns would still be described as backend. I ignore any opportunity described as fullstack.