“there's more there's more Java in in the stripe of 2023 than there was in the stripe of 2016”
← All resourcessoftware
Java
By James Gosling
1 recommend/use · 2 sourced episodes
Every sourced reference
Short attributed excerpts only. Timestamps are approximate.
“then Java became a thing”
Related frameworks
Self-Mastery5 steps
Choose Your Abstraction Layer Deliberately
Delegate the work you don't enjoy to a higher abstraction; keep the parts that make you good and happy.
Read →
Communication6 steps
Energy-Aligned Writing
Write only what energises you, only what overlaps your job, and publish nearly all of it.
Read →
Productivity5 steps
Imperfect Metrics as Education
Report an imperfect engineering metric on purpose, then use every question about it to educate upward.
Read →
Innovation4 steps
Problem-First AI Adoption
Start from the customer problem and ask where AI helps — never from 'what do we do with AI?'
Read →
Strategy5 steps
Stocks-and-Flows Pipeline Diagnosis
Model any org process as stocks and flows, then find where reality disagrees with the model.
Read →
Leadership5 steps
Take People With You Before You Fix Anything
A new leader's toolbox is worthless until the team agrees a problem exists — build the why first.
Read →
Strategy5 steps
The Boring Engineering Strategy
Write the strategy down, get the diagnosis honest, then constrain options so energy goes to what matters.
Read →
Leadership4 steps
The Honest-Applicable-Reversible Values Test
Three tests that separate values which drive decisions from values that just describe your self-image.
Read →
Innovation6 steps
The Horizon-3 Research Team That Ships
Fund a 3-5 year research team, then bolt it to product so ideas actually reach production.
Read →
Leadership5 steps
The Input-Metrics Stack for Developer Productivity
No single metric rules them all — combine per-component input metrics that ladder up to time-to-value.
Read →
Leadership5 steps
The Shared-Fate EM/PM Pair
Give the eng manager and PM the same performance rating, and make them understand before they argue.
Read →
Innovation5 steps
The Zero-Ask Assistant (Copilot Design Philosophy)
If the user has to ask for it or wait for it, they won't adopt it — build assistance that infers.
Read →
People in these episodes
Related resources
- Accelerate
- Accenture
- Airbnb
- All the Light We Cannot See
- Amazon
- Amazon Prime Video
- Amazon Web Services
- An Elegant Puzzle
- Apple Podcasts
- Atlassian
- AWS
- Calm
- Carta
- Chameleon
- ChatGPT
- Dare to Lead Like a Girl
- Don't Think of an Elephant!
- DORA
- DX
- Failing Forward
- GitHub
- GitHub Advanced Security
- GitHub Copilot
- GitHub Next
- Good Strategy/Bad Strategy
- Good to Great
- Google Cloud
- Google Reader
- Google Search
- Greenhouse
- HelpBar
- How Big Things Get Done
- IBM
- Jira
- Jira Product Discovery
- Lenny's Podcast
- Lenny's Podcast website
- Medium
- Microsoft
- Microsoft Azure
- Netflix
- OneSchema
- OpenAI
- Python
- Ruby
- Sanity
- Shopify
- Slack
- SPACE
- Spotify
- Stripe
- Substack
- Technology Strategy Patterns
- The Crux
- The Phoenix Project
- The Value Flywheel Effect
- The Wheel of Time
- TomTom
- Top Chef
- Uber
Spot an error or want this page removed? Request a correction or removal.