pure backend/data roles are interesting because when building infra for multiple consumers, you can give many teams leverage over their problems. It’s like buil

pure backend/data roles are interesting because when building infra for multiple consumers, you can give many teams leverage over their problems. It’s like building a great tool they didn’t have before. For some people this feels immensely satisfying. Especially when they get immediate feedback from fellow devs. In search, for example, I’ve seen teams turn Elasticsearch reindexing from a task that takes weeks down to hours. So many teams can build on that and it unlocks tremendous abilities for them to even care about improving search. > Data roles heavily focus on particular enterprise products (Kafka, Redshift, Snowflake) at the expense of engineering fundamentals. I’ve heard the opposite, ha! That “App dev roles rely on just prebuilt web frameworks and canned RDMSs, not the breadth of the full menu of fundamental problems out there” :-p. In reality there’s a huge menu of databases and data processing systems that backend/data roles play with from spark, flink, Kafka, analytical systems and so on…