ADVANCED · 8 MODULES · 64 LESSONS

The Architect's Craft

Get your architecture decisions to stick even without formal authority: tailor how you communicate them, align your teams, and explain trade-offs in business terms.

For you if
You're a senior dev or tech lead stepping into an architect role without authority over the team.
By the end
You'll know how to use Conway's Law in your favor, diagram with the C4 model, write documentation that lasts, and design for change.
You need
Experience leading technical decisions on a team, and Python to run the guide's metrics.
  1. 01Qué hace de verdad un arquitecto8 LESSONS
    1. Module introduction: what an architect actually does
    2. The ivory tower myth
    3. The architect stays close to the code
    4. Reversible over right
    5. Enabling, not dictating
    6. The bottleneck trap
    7. BDUF versus the last responsible moment
    8. Mini-project: diagnose and redesign the architect role at Mercado
  2. 02La Ley de Conway8 LESSONS
    1. Module introduction: you ship your org chart
    2. You ship your org chart: the law, measured
    3. The monolith is your first org chart
    4. The cost of coordination
    5. The modules that cross team boundaries
    6. The inverse Conway maneuver
    7. Team topologies
    8. Project: redesign Mercado's organization for a new capability
  3. 03Comunicar la arquitectura8 LESSONS
    1. Module introduction: communicate to be understood, not to archive
    2. The C4 model: four levels of zoom
    3. Context and Container: the two maps you almost always need
    4. Component and Code: when to go down and when to stop
    5. The right diagram for the audience
    6. The ADR as communication: the why that travels through time
    7. Avoiding the 500-page document and the spaghetti diagram
    8. Project: communicate Mercado's architecture for two audiences
  4. 04Liderazgo técnico sin autoridad8 LESSONS
    1. Module introduction: leading without being able to command
    2. Influence instead of mandate
    3. Borrowed authority: the trust account
    4. Guardrails instead of gates
    5. Disagree and commit
    6. The conversations that hold up the architecture
    7. Building technical consensus
    8. Project: get 5 squads to adopt a standard
  5. 05Stakeholders y atributos de calidad8 LESSONS
    1. Module introduction: from the business's wish to the quality attribute
    2. From the business goal to the quality attribute
    3. The quality attribute scenario: making the vague measurable
    4. Architecturally significant requirements: the signal and the noise
    5. The implicit attributes nobody asked for
    6. Speaking the stakeholder's language
    7. Knowing how to say no (and the cost of yes)
    8. Project: derive Mercado's quality attributes for a launch
  6. 06Diseñar para el cambio8 LESSONS
    1. Module introduction: designing for change
    2. The architecture is never final
    3. Keeping the doors open
    4. Sacrificial architecture
    5. The YAGNI line
    6. Painting yourself into a corner
    7. Designing the seams
    8. Project: design Mercado's evolution for a change
  7. 07Documentación que sobrevive8 LESSONS
    1. Module introduction: documentation that survives
    2. Living documentation
    3. Docs-as-code
    4. The C4 + ADR + arc42 system
    5. Document the stable, not the volatile
    6. The README that onboards
    7. Bus factor and knowledge sharing
    8. Project: make Mercado's documentation survive
  8. 08Proyecto capstone — sé el arquitecto de Mercado ante un cambio8 LESSONS
    1. Capstone presentation: the craft as one single movement
    2. Frame the role and the assignment
    3. Derive the quality attributes from the goal
    4. Apply the inverse Conway maneuver
    5. Produce the C4 and the ADR
    6. Lead the rollout without authority
    7. Plan the evolution and the documentation
    8. Project: be Mercado's architect facing the change
Reviews

What students say

These reviews are from enrolled students who completed at least 50% of the course. We moderate reviews only on content grounds (spam, offensive language, personal data), never for being critical or negative.

No approved reviews yet.

Be the first to share your experience!

SEC. 06 · THE STUDIO

Why this studio exists

For decades, building software belonged to technical profiles with years of training, and getting a digital product into the real world took companies months or years. No-code and AI have narrowed that gap, but the knowledge is still held by a few.

Tech Benders exists to open that knowledge up, so business teams and non-technical teams can put their ideas into production with the right technical decisions behind them. AI does what you ask of it. Without a technical base, what it builds may not scale with your company’s ecosystem, and its costs can run away over time.

The team knows the pains of large organizations and the speed at which they have to move. It brings solution architecture, data engineering, product built end to end from back end to front end, and daily work with AI. Software that solves what you need in days, not months, with the cost of AI kept in check.

Founders

The studioRead about Tech Benders →

Write to ushi@techbenders.io

Made with Wislab