job) if I cannot write code” 2. “I won’t be able to provide good feedback if I cannot understand how things work and do it myself. People won’t trust me or my opinion” 3. “I won’t understand new technologies” 4. “It will be harder to have empathy for my teammates without knowing how easy it is to do or understand something in our systems” Right? Anything else?
LEVERAGE to help our team? What’s in it for them to have us as their managers? 1. Design requirements, trade offs, risks, teach 2. Operate sustainability, quality of life, focus 3. Hire puzzle, level up, momentum 4. Envision pitch, alignment, personal growth
to have empathy for my teammates without knowing how easy it is to do or understand something in our systems” 30% in the present: Write code in areas you’ll gain insights and feel pains → Level up Design & Operate 70% in the future: Research for missing knowledge your team is lacking → Level up Envision & Hire A day per week? More? Less? Hours should fluctuate, keep the ratios
was it invented) Seek to understand how things work. fundamentals. How to choose the right level of data consistency for the app’s reads/writes? Who invented Spark? What was missing at the time? How is it different? How Virtual DOM works? What should I worry about when using event-loop based framework? Why Kafka is using append-only log? What becomes more difficult when using microservices?
Decisions - Replicated Data Consistency Explained Through Baseball - Silence is Golden: Coordination-Avoiding Systems Design - Turning the database inside out
Would you like to go much deeper into the 70%? Ping me for a workshop I plan... Feedback? Questions? Say hello 👋 [email protected][email protected] Build empathy. Understand the fundamentals. Live in the future.