You Don't Need to Master It to Teach It—And Teaching Is How You Actually Learn
I taught resiliency automation to a teammate a month after learning it myself. Here's why admitting what I don't know made me a better engineer faster.
A month ago, I was sitting through step-by-step walkthroughs on resiliency automation. This week, I walked a teammate through the exact same process.
She hit the same wall I did: Confluence documentation everywhere, zero clarity on what goes where. So instead of sending her the written instructions I'd received, we jumped on a call. I showed her my work, live.
Here's what surprised me: I'm not an expert. Not even close. But I was useful anyway.
Breaking Down What Actually Stuck
The resiliency automation work has two hard parts: the CI code portion and the CD portion. The CD part is where people get lost—it's where I got lost.
When I walked my teammate through it, I didn't explain why the architecture works. I explained what I had to figure out:
- Where do the variables live?
- What files are completely new?
- Which existing files do we touch, and where?
- What's application-specific vs. what's the same every time?
I wrote down the steps from scratch, the messy way I learned them. That turned out to be more useful than polished documentation.
The Honest Part
I don't fully understand resiliency automation end-to-end. And I told her that.
What I do know is what I struggled on. I know which parts need senior review before we ship. I know the difference between "I'm not sure yet" and "I'm confident this is right."
Teaching from that honest place—knowing my own ceiling—let me be clear about what she should trust and what needs a second set of eyes. That's actually more valuable than pretending I have it all figured out.
What Teaching Actually Did to Me
Halfway through explaining it to her, I realized how much I'd grown in four weeks. The day-to-day feels slow. You're stuck, unblocked, stuck again. Progress isn't visible. But the moment I had to explain the work—not just do it—I saw the shape of what I'd learned. The concepts clicked harder. The "why" became real.
That's the thing nobody tells you: explaining something to someone newer doesn't require mastery. It requires honesty. And honesty accelerates your own learning faster than months of solo grinding.
What I'd Tell You If You're Stuck Right Now
If you feel like you're moving at a crawl, find someone two weeks behind you and walk them through what you've learned. Don't wait until you're an expert. Don't polish the narrative. Just show them how you figured it out.
In that process, you'll see:
- What you actually understand
- What you're still guessing on
- Where your growth is (even if it felt invisible)
And that builds confidence. Not the fake kind. The grounded kind, where you know your edges and trust yourself to find help when you hit them.
That's the day the learning stops feeling slow.