01
SCALE · SECURITY · DELIVERY
220+ pipelines. One security program.
How do you introduce security scanning across hundreds of CI/CD pipelines without turning delivery into a bottleneck?
What it taught me: Technical programs rarely fail because of one technical problem. Dependencies, ownership, sequencing and communication matter just as much.
02
CLOUD · DEPENDENCIES · CHANGE
“Just migrate it to the cloud” isn't a plan.
What changes? What doesn't? Who owns the dependencies? What could break? How do we validate it?
What it taught me: You don't need to design the architecture yourself. But you need to understand enough of it to see the gaps.
03
ARCHITECTURE · ENGINEERING
From monoliths to microservices.
Architecture decisions aren't just engineering decisions. They affect timelines, testing, dependencies, teams and operational complexity.
What it taught me: You don't need to be the architect in the room to ask an architect a really good question.