No. 021
Engineering
The Software Crisis 2026: Why More Code Doesn't Mean More Value
The software crisis 2026 isn't about writing code. It's about knowing what NOT to build when AI generates infinite output.
Notes from the field
Product engineering notes from the field.
66 published notes
Latest dispatches
No. 018
Engineering
Product Engineering Culture: What It Looks Like at High-Growth Companies
Product engineering culture in practice at PostHog, Linear, Vercel, and Figma. Concrete structures, rituals, and principles that drive shipping velocity.
No. 017
Engineering
AI Skills vs Agents: Don't Build Agents, Build Skills
AI skills vs agents: why discrete, composable capabilities beat monolithic agents, and how product engineers design them.
No. 014
Engineering
Product Engineering for Enterprise Teams: Scaling Ownership
How to adopt product engineering in enterprise orgs with 100+ engineers. A phased rollout playbook covering governance, metrics, and team structure.
No. 008
Engineering
The Product Engineer Tech Stack in 2026
The complete product engineer tech stack for 2026, organized by Define, Build, and Ship phases. Tools for discovery, development, deployment, and measurement.
No. 007
Engineering
How to Transition Your Engineering Team to Product Engineers
A 90-day playbook to transition engineers to product engineers. Covers resistance patterns, org design, metrics, and leadership tactics for VPs and directors.
No. 006
Engineering
Product Engineering Team Structure: How to Organize for Ownership
How to restructure from PM+Eng silos to a product engineering team structure. Ratios, reporting lines, and transition playbooks for engineering leaders.
7 notes