Forged in Sao Paulo, tuned for distributed squads
Stream Node began as late-night whiteboard sessions between platform leads who wanted review rituals that survived re-orgs. Today we still bias toward tangible artifacts — maps, ADRs, diagrams in CI — over slide-only narratives.
Principles
- Heat in the room should match heat in production — no toy examples without escape hatches.
- Facilitation notes are as important as slide decks.
- We document what we skipped so teams know where to dig next.
- Mentors rotate so no single voice becomes the house style.
Milestones
- 2017 — first closed-door architecture review clinic for a logistics API team.
- 2021 — hybrid cohorts with async critique lanes launched for cross-state squads.
- 2025 — editorial blog and public syllabus drops added for alumni who wanted reusable narratives.
Core team
Helena Moraes
Architecture lead
Maps messy org charts to bounded contexts and keeps naming workshops from boiling over.
João Carvalho
Systems mentor
Coaches teams on reliability drills without turning postmortems into blame parades.
Priya Nambiar
Review facilitator
Designs review agendas that capture dissent without losing the clock.
Vivian Costa
Program manager
Keeps cohort calendars honest and translates architecture work into promotion-ready narratives.
Lucas Azevedo
Systems mentor
Specializes in payment flows, idempotency keys, and diagram hygiene in CI.
Diego Salles
Review facilitator
Trains staff engineers to give critique that references diagrams, not personalities.
Marina Kato
Architecture lead
Bridges data platform vocabulary with squad-level delivery rhythms.
More cohort voices
"Portfolio Defense for Principal Promotion Packets forced me to cite Sequence Diagrams That Survive Production artifacts instead of vibes. Mock panel was blunt; still processing the feedback on brevity."
"Review Practice Clinic — role cards kept timeboxing honest. One session felt rushed for remote folks; async replay helped."
"Service Boundaries for Mobile Release Trains highlighted our silent DTO coupling. Contract testing lab needed more Kotlin samples, but the release train matrix alone paid for the seat."
"Architecture Metrics That Product Teams Read: PM pushback roleplay was awkward and necessary. ★★★★☆ because I wanted one more metrics dictionary entry."
"Latency Budgets for Edge POP Planning — finally a deck our capacity-planning partners did not hand-wave."
"Engineering team at a consultant shop: Context Maps for Distributed Teams glossary export went straight into onboarding; facilitators kept us from naming everything "Core"."
"Decision Records for Heated Design Reviews gave us a rubric our security partners actually filled in. Still tightening how we attach diagrams, but the review cadence stuck."