Sounds like you're more interested in "solving the business problem" and less interested in "solving the problems of the code that is solving the business probl

Sounds like you're more interested in "solving the business problem" and less interested in "solving the problems of the code that is solving the business problem." Hillel Wayne recently wrote about this distinction: > New Newsletter! An exploration of a core difference between "programming" and "software engineering": how much you work on "solving the business problem" versus "solving the problems of the code that is solving the business problem." https://twitter.com/hillelogram/status/1486079674795143170 https://twitter.com/hillelogram/status/1486079674795143170 https://buttondown.email/hillelwayne/archive/software-artifacts-and-programming-vs-engineering/ https://buttondown.email/hillelwayne/archive/software-artifa... And sounds like you enjoy "product engineering" more than "infrastructure engineering." Michelle Lim wrote a post about it, which was discussed on HN. > Try using the "Product/Infrastructure" axis as the first axis to understand your career preference. > Broadly speaking, there are 2 types of engineers: "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. https://news.ycombinator.com/item?id=28476538 https://news.ycombinator.com/item?id=28476538 https://www.michellelim.org/writing/stop-using-frontend-backend/ https://www.michellelim.org/writing/stop-using-frontend-back...