“he told Jason I want to try building this in Ruby”
Ruby
By Yukihiro Matsumoto
4 recommend/use · 4 sourced episodes
Every sourced reference
Short attributed excerpts only. Timestamps are approximate.
“we use Ruby Ruby was not that fast Shopify would rather have it very fast”
“another good example at at stripe was this idea of we run a a ruby monolith”
“at Stripe we write a lot of code in Ruby”
Related frameworks
Alpha Co-Creation Loop
Pick the users who are already pushing the boundary, build with them in a shared channel, ship only when they're thrilled.
Energy-Aligned Writing
Write only what energises you, only what overlaps your job, and publish nearly all of it.
First-Principles Re-Derivation (Rerun the Decision Tree)
Rebuild any product decision from today's building blocks instead of copying path-dependent solutions.
Fixed Time, Variable Scope (Appetite-Based Planning)
Set the max time you'll spend first, then design a solution that fits it — instead of estimating a concept.
Framing (Setting the Boundaries)
Narrow a fuzzy request down to the specific problem worth solving before you design any solution.
Friction Logging
Adopt a specific user's identity, walk your own product end-to-end, and log every point of friction.
Group UX Review and Walking the Store
Taste the soup together — experience the product as a group, log issues live, then debate each one.
Hire for Autonomy: References, Real Work, and Default Trust
You'll be in none of the decisions that matter — so hire people you can hand autonomy to, and verify via references.
Imperfect Metrics as Education
Report an imperfect engineering metric on purpose, then use every question about it to educate upward.
Internal Tools as a Product (The Crying Octopus)
Run your dev-productivity team like a product team: monthly surveys, hard metrics, and one-click paper cuts.
Live Shaping Session
Put product, a senior engineer, and a designer in a room to sketch and break ideas until one is clearly buildable in the appetite.
Lower the Courage Required
The scarcest resource is courage, not genius — so design products and decisions to need less of it.
Positional vs. Tactical Game
Don't die, then pour your energy into board position — tactics are the drawdown of value you've already earned.
Positive-Sum Dials (Levers You Don't Pull)
Build every monetization lever you can, then refuse to pull them — coordinate on the iterated game instead of defecting for short-term profit.
Ship Fast Without Breaking Money
Reject the reliability/velocity trade-off: automated gauntlet, ramped exposure, and remediations ahead of roadmap.
Stocks-and-Flows Pipeline Diagnosis
Model any org process as stocks and flows, then find where reality disagrees with the model.
The Boring Engineering Strategy
Write the strategy down, get the diagnosis honest, then constrain options so energy goes to what matters.
The Circuit Breaker (Back to Shaping)
When a project overruns its appetite, don't extend it or gut the agreed value — pull it back into shaping mode.
The Detail Dial
Calibrate how prescriptive a shaped plan is to the builder's seniority — more detail lifts juniors, less frees seniors.
The Engineer-cation
Leaders clear 3-4 days, join a team as an IC, ship one small feature to production, and log the friction.
The Honest-Applicable-Reversible Values Test
Three tests that separate values which drive decisions from values that just describe your self-image.
The Inverted W Planning Process
Teams propose, leaders synthesise, teams adjust, leaders resynthesise, orgs distribute with context.
The Nine-Scopes Kickoff
At kickoff, have the builders translate the shaped idea into nine-or-fewer implementation chunks to test scope and build clarity.
The Shared-Fate EM/PM Pair
Give the eng manager and PM the same performance rating, and make them understand before they argue.
The Talent Stack (Intersection of Uniqueness)
Stack three-to-five things you're uniquely good at and curious about so you know more than everyone else in that tiny space.
The Toby Tornado (Compressed Change Management)
When you sense a project is wrong, compress the conflict into a short window, kill it, and reconstitute the team as founders of the next version.
Unquantifiable-First Decision-Making
Demote metrics to a support function and let taste, fun, and delight drive — because Goodhart's law means any metric-as-goal degrades.
People in these episodes
Related resources
- 1,000 True Fans
- 37signals
- Accelerate
- Airbnb
- Airtable Product Central
- Amazon
- Amazon Web Services
- An Elegant Puzzle
- Andrej Karpathy's YouTube channel
- Apple Podcasts
- Atlassian
- AWS
- Basecamp
- Build
- Calm
- Carta
- ChatGPT
- ChatGPT Plus
- Coinbase
- Competing Against Luck
- Cursor
- Demand-Side Sales 101
- Discord
- Don't Think of an Elephant!
- DORA
- DX
- Figma
- Finite and Infinite Games
- GitHub Copilot
- GitHub Enterprise
- Good Strategy/Bad Strategy
- Google Calendar
- Google Cloud
- Google Docs
- Google Reader
- Google Search
- GPT-4
- Granola
- Greenhouse
- High Output Management
- How Big Things Get Done
- IBM
- Java
- Jira
- Jupyter Notebook
- Lenny's Newsletter
- Lenny's Podcast
- LennyPodcast.com
- Linear
- Link
- Liveblocks
- Loom
- Medium
- Merge
- Microsoft Azure
- Midjourney
- Netflix
- Notion
- OneSchema
- OpenAI
- Perplexity Pro
- Pirate Gold
- Python
- Scaling People
- Shape Up
- Shopify
- Sinch
- Slack
- SPACE
- Spotify
- Stack Overflow
- Stanford University
- Stripe
- Stripe Atlas
- Stripe Billing
- Stripe Connect
- Stripe Sessions
- Substack
- Superhuman
- Technology Strategy Patterns
- The Crux
- The Last Dance
- The Phoenix Project
- The Value Flywheel Effect
- TikTok
- Top Chef
- Uber
- Warrant
- Wikipedia
- WorkOS
- World of Warcraft
- Y Combinator
- YouTube
- Zanzibar
- Zoom
Spot an error or want this page removed? Request a correction or removal.