Dependencies
9 posts filed under Dependencies.
Sizing Your Orchestrator To Your Team, Not Your Ambition
Three engineers maintaining Kubernetes Airflow for 20 DAGs is a sizing mistake, and a common one.
Read →Software Modernization Is Not Architectural Modernization
Software modernization and architectural modernization are different problems with different fixes.
Read →The Data Product Canvas (One-Page Definition)
An empty "consumers" field is the signal to deprecate the asset. Most teams ignore it.
Read →The Tech Lead's Real Job Isn't Technical
You got promoted for coding. Now your job isn't to code.
Read →Dependencies - Hidden Drags on Progress
Your roadmap isn't delayed by complexity. It's delayed because of coupling.
Read →Platform as Product - Enabling Team Autonomy
Your platform team believes they're building infrastructure, but they're actually running a product company with just one customer segment: …
Read →If you organise by technology rather than by outcome, you...
If you organise by technology rather than by outcome, you'll deliver patchwork.
Read →Slideware isn't strategy.
Slideware isn't strategy. If it can't survive constraints, it's theatre.
Read →Your architecture is how you deliver.
Your architecture is how you deliver. Slow isn't about the team. It's about the design.
Read →