💡

InsightHunt

Hunt the Insights

D

Dhanji R. Prasanna

Episode #74

Chief Technology Officer

Block (formerly Square)

⚡Execution👥Team & Culture🎯Product Strategy

📝Full Transcript

15,091 words
Lenny Rachitsky (00:00:00): There's a lot of talk about productivity gains through AI. There's this camp of people that are so overhyped, nothing's working, nobody's actually adopting this at scale. Dhanji R. Prasanna (00:00:07): We see a significant amount of games. We find engineering teams that are very, very AI forward are reporting about eight to 10 hours save per week. Whenever I hear a stat like this, I think an important element is this is the worst it will ever be. This is now the baseline. The truth is the value is changing every day, so you need to ride that wave along with it. Lenny Rachitsky (00:00:27): There's a story I heard you share on a different podcast where there's an engineer who has Goose watching. Dhanji R. Prasanna (00:00:31): You'll be talking to a colleague on Slack or an email, and they'll be discussing some feature that they think is useful to implement. Now a few hours later, he'll find that Goose has already tried to build that feature and opened a PR for it on Git. Lenny Rachitsky (00:00:43): What level of engineer is most benefiting from these tools? Dhanji R. Prasanna (00:00:47): What's been surprising and really amazing, the non-technical people using AI agents and programming tools to build things, the people that are able to embrace it to optimize for their particular workday and their particular set of tasks are really showing the most impact from these tools. Lenny Rachitsky (00:01:07): How do you think things will look in a couple of years in terms of how engineers work that's different from today? Dhanji R. Prasanna (00:01:12): All these LLMs are sitting idle overnight and on weekends, while humans aren't there. There's no need for that. They should be working all the time. They should be trying to build in anticipation of what we want. Lenny Rachitsky (00:01:24): What's maybe the most counterintuitive lesson you've learned about building products or building teams? Dhanji R. Prasanna (00:01:29): A lot of engineers t...

💡 Key Takeaways

  • 1AI productivity is currently at its baseline; the 8-10 hours saved per week today is the 'worst' it will ever be.
  • 2Transition from 'Vibe Coding' (chatting with AI) to 'Agentic Autonomy' where AI works overnight while humans sleep.
  • 3Use the Model Context Protocol (MCP) to wrap internal tools (Snowflake, Jira, Calendar), giving LLMs the ability to execute actions, not just generate text.
  • 4Conway's Law is absolute: To change your technical output, you must change your organizational structure from GM-led silos to functional pillars.
  • 5Non-technical teams (Legal, Risk, Support) often see higher immediate ROI from AI agents than engineering teams by building their own internal tooling.
  • 6Code quality and product success are uncorrelated (e.g., YouTube's early messy codebase vs. Google Video's clean failure).
  • 7Before optimizing or automating a process with AI, ruthlessly question if the process needs to exist at all.

📚Methodologies (3)

The Agentic MCP Framework

by Dhanji R. Prasanna

⚡ Execution

A strategy to move beyond passive LLM interaction by wrapping internal tools in the Model Context Protocol (MCP). This gives AI the ability to autonomously interface with systems (databases, calendars, IDEs) to complete complex, multi-step workflows without human hand-holding.

Core Principles

  • 1.Wrap Tools, Don't Just Paste Context: creating standardized API wrappers (MCPs) for internal systems (Snowflake, Slack, Git) so the agent can fetch its own data.
  • 2.Shift to Asynchronous Autonomy: Instead of waiting 3 minutes for a response, assign the agent 8-hour tasks (e.g., 'refactor this module', 'fix these vulnerabilities') to run overnight.
  • 3.The 'RM -RF' Mindset: Use the agent's speed to delete and rewrite entire applications from scratch rather than incrementally refactoring legacy code.
  • +1 more...

"Goose gives these brains arms and legs to go out and act in our digital world... It’s orchestrating across all these systems."

#agentic#execution#process
View Deep Dive →
The Functional Tech-First Reset

by Dhanji R. Prasanna

👥 Team & Culture

A restructuring methodology that pivots from General Manager (GM) led business units to functional reporting lines. This unifies engineering standards, prevents the commoditization of developers, and enables rapid, company-wide technology adoption (like AI).

Core Principles

  • 1.Unify Reporting Lines: All engineers report to a centralized Engineering Head, not a Business Unit GM, to ensure technical depth over short-term business KPIs.
  • 2.Standardize 'Tech Identity': Ensure a 'Senior Engineer' title means the same thing across all products (Cash App, Square, Tidal) to allow fluid talent movement.
  • 3.Stop Commoditizing Headcount: Move away from 'Mythical Man-Month' hiring (adding bodies to ship faster) toward leveraging shared platforms and high-leverage tools.
  • +1 more...

"I think that moving to a functional structure completely changes that... we no longer see engineers as a commodity to just add 100 people to go and build the next product."

#functional#tech-first#reset
View Deep Dive →
🎯 Product Strategy

A disciplined approach to innovation that insists on starting with micro-teams solving hyper-specific personal problems before scaling to a platform or product.

Core Principles

  • 1.The 'Cup of Tea' Rule: Don't boil the ocean to make tea. Solve the immediate, small problem fully before expanding scope.
  • 2.The Personal Itch Test: Founders/builders must use the tool for a personal workflow (e.g., organizing family receipts) to discover real edge cases.
  • 3.Question Base Assumptions: Before building a tool to optimize a process, ask 'Does this process need to exist?' (e.g., deleting tests vs. optimizing test runners).
  • +1 more...

"If you want to make an apple pie from scratch, you have to first invent the universe... narrow your scope to the thing that's in front of you."

#scientist'#prototyping#strategy
View Deep Dive →
← Browse All Episodes