▲Takeaway15:00
Check Your Spec Into the Repo So Claude Can Review Against It
Fiona's key unlock for automated code review is giving Claude an explicit framework of what "good" looks like. Any statement of quality — a content-design scale, a spec — should be checked into the repo and kept in sync with the code, so Claude Code review can validate every change against it.
- Claude reviews reliably when given an explicit framework to validate against
- Check specs and 'what good looks like' statements into the repo
- Keep the spec updated alongside the code, frequently
- Human reviewers still handle areas needing deep subject-matter expertise
“Claude is very good when you give it a framework to validate against those frameworks.”
“any time you have like a statement of what good looks like, get that into the repo and then Claude code review can make sure…”
#code-review#specs#quality#claude-code
▲Takeaway17:00
The Two Profiles Fiona Hires For Now
For the Claude Code team, Fiona hires two profiles: creative builders with product sense who own a product end-to-end, and deep systems experts for the hard parts that still need verification. She realized early the team had strong product generalists but was missing distributed-systems depth.
- Profile 1: creative builders/'dreamers' with product sense who iterate, polish, and own end-to-end
- Profile 2: deep subject-matter/systems experts for the parts that need verification
- The team was strong on product generalists but short on systems and distributed-systems depth
- 'Trust but verify' — invest human expertise wherever verification is critical
“the two profiles that you now look for when you're hiring are creative builders with product sense and deep systems experts for the hard parts.”
“it's all about trust but verify. The models are really good, but there are definitely a lot of areas that still need verification.”
#hiring#team-building#engineering#systems
▲Takeaway20:00
Why Some Engineers Thrive on AI and Others Resist: Growth Mindset and Fear
Fiona attributes thriving in the AI transition to a growth mindset — always learning, and accepting that what made you successful may no longer serve you. She sees frustration as often rooted in fear, and her advice is to lean in and ask what's within your control, reframing change as happening 'for you' rather than 'to you.'
- Growth mindset = always learning; past success habits may need to change
- Frustration often masks fear and a feeling that everything is outside your control
- Antidote: find one action within your control; shift from 'happening to me' to 'happening for me'
- Do something scary occasionally — you'll dip while learning, but that's how you keep growing
“for anything that you know, that that there is a fear my advice is kind of lean in and ask, "Okay, is there some what…”
“the cave you fear contains the treasure you seek.”
#mindset#fear#career#growth
▲Takeaway38:30
High Agency Comes With High Accountability
Agency is a core value on the Claude Code and Cowork teams — everyone gets the freedom to propose how to solve a problem. But Fiona pairs it with accountability: freedom to build is balanced by owning the outcome and having a clear hypothesis of what you're trying to solve.
- Everyone on the team owns ideas for how to address a problem
- High agency is deliberately coupled with high accountability
- Accountability ties back to having a clear hypothesis of what you're solving
“it's really high agency and then we say with high agency is also high accountability. So it's all about like making sure folks have that…”
#agency#accountability#culture#management
▲Takeaway49:30
Every Manager Starts as an IC — and Keeps Doing PRs
Fiona has new managers begin as individual contributors before taking on people responsibility, giving them maker time to learn the codebase and build rapport as a teammate first. Even for herself, the PRs she does matter less for what they fix than for keeping her in the flow and in daily touch with a fast-changing product.
- New managers start as ICs to learn the codebase before shouldering people responsibility
- Doing the work first builds genuine rapport with the team
- Fiona's own PRs are about staying in touch with the product, not the fix itself
- Leaders who don't live and breathe the product lose touch and feel for it
“even me doing PRs it's less about what it is I'm fixing, it's more about me using the the product every day just to keep…”
#management#player-coach#leadership#dogfooding
▲Takeaway1:03:30
Dogfood Relentlessly — and Trust the Anecdote Over the Data
Fiona's defining habit is using the product she builds constantly, which surfaces things dashboards miss — a scam vector on Marketplace, floor-height bugs in VR she uniquely reproduced. She and Lenny land on the Bezos principle: when you have both the data and an anecdote, trust the anecdote, and if you can't use the product, meet customers instead.
- Constant dogfooding keeps a leader's pulse on the real product experience
- Personal use surfaced a Marketplace scam vector and VR floor-height bugs others missed
- Bezos: with data and an anecdote in conflict, trust the anecdote
- If you can't use the product, do customer visits — a Chile trip revealed slow-LTE feed loading blocking growth
“that's how you keep your pulse on the product that you're building and don't get too lost in metrics and dashboards only or presentations.”
“I think it was Jeff Bezos that said if you have the data and you have an anecdote, trust the anecdote over the data.”
#dogfooding#customer-research#product#leadership
▲Takeaway1:23:00
Explicit Permission to Kill Processes — and Just-in-Time Planning
A pillar of the Claude Code and Cowork culture is explicit permission to kill any process that no longer serves the team. Fiona applied it to her own planning: a six-month roadmap went stale within three months, so she moved to 'JIT planning' — a lightweight monthly priority spreadsheet checked weekly to confirm it's still current.
- Team norm: explicit permission to kill noisy, expensive, or dreaded processes
- Test any process by asking whether it still serves its purpose
- A six-month roadmap became stale in three months as the landscape changed
- JIT (just-in-time) planning: a lightweight monthly priority sheet, re-checked each week
“one other thing that's really big on Cloud Code and Core team culture is explicit permission to kill processes that no longer serve us.”
“I I call it JIT planning now, like just-in-time planning.”
#planning#process#culture#management