Topic Backlog

1:1s and how to use them. Link back to context and decisions

Books — how they’re helpful

Limit testing reports

Saying no

Architecture and what it means

Product will have ideas. Ideas are relatively cheap and will have high noise to signal. Engineering needs to also have their own conviction as we know what’s feasible vs not. There is a natural push and pull.

Vertical agents are better and theories on how it translates to teams

Heros

Studio vs factory

Handling being understaffed

Metrics. When theyre needed

Good metrics. Bad metrics.

Paying for Acceleration

Vision vs strategy. Problem vs solution

Role compression

Conways law

Delegation

Proof of concept and scale cycle

Managing up

Roi of time is not uniform

Tools and levers

What is tech debt. >1 ways of doing same thing. 1) Incorrect assumptions and 2) limited context lead to tech debt. Latter can be solved through documentation. 1) leads to if/else and/or overly custom and non standard way to approach the problem so it cannot be reused

Migrations and why theyre important —> adapt to new assumptions. Essential to fast growing org

Microservices / micro repo

Tech foundations earning the right

Tech foundations as ip

Context as the point of all disagreement

Aligning on terminology

Systems thinking to management

Time and resources is the only moat —> open communication is best