18 karma · joined July 29, 2022
Spot on. This is massively important. Not only will you build a better picture of systems as a whole, but you'll also discover what is interesting and not interesting to you. Finding that out early on is invaluable.
Favorite quote from the article.
____
I think the concept of dirty work is important but isn't always as fruitful of a pursuit as the author makes it seem. There are plenty of cases of dirty work success stories, but there are just as many stories of automated runbooks that never end up being used or documentation never read.
What's important is to understand high signal dirty work. Listen for what is truly causing pain within a team or across teams and begin to pull on that thread. Talk to the stakeholders. Understand the ins and outs of the problem. Then go down the rabbit hole of getting hands dirty.
Hello! I'm the CTO at Beautiful Technologies Inc. where we are building peer-with-peer social e-commerce to change online shopping forever.
A few notes on us:
- Founding team of Ex-AWS employees
- VC backed pre-seed round of funding
- Generous equity packages and benefits
- Ability to build from zero to one
Our current tech stack is React Native frontend, Apollo GraphQL API, Node.js w/ Typescript, deploying on AWS. Product is very early stage.
Reach out over LinkedIn if you'd like to learn more or this sounds interesting! https://www.linkedin.com/in/david-dalmaso-359791101/