Read the original at Lenny’s Newsletter ↗lennysnewsletter.com · subscriber post
By Lenny Rachitsky · lennysnewsletter.com · @lennysan on X · YouTube · LinkedIn
Lenny answers a reader who lacks a technical background and struggles to follow engineers and make trade-off decisions. He lays out a three-step path: learn core concepts like how software systems, APIs, and databases work, ask engineers targeted questions, and eventually build something yourself. The post is a practical roadmap for becoming a more technical, effective PM without necessarily learning to code first.
Subscriber post — summary only01Key takeaways
- Basic knowledge of how software systems, web apps, APIs, and databases work gives PMs a strong foundation quickly.
- Engineers are usually glad to explain their work, so questions about architecture and workflow are a valuable learning source.
- Asking how a feature would move from idea to launch reveals real effort, dependencies, and bottlenecks.
- Learning to code is the deepest level of technical skill, but it is optional for gaining most of the benefits.
- Technical fluency compounds over time, so consistent small investments beat a single crash course.
Summary and takeaways written by PM Atlas; quotes are short excerpts. © the original author.