Build trust by understanding the client's business

  • Pocock qualifies his advice: his audience and reputation preceded his consulting work, so he has limited experience competing cold for engagements. 20:56 21:46
  • He suggests using a fast prototype to demonstrate that you understand a client's business and care about the same outcomes. In this exploratory setting, he considers rapid vibe coding useful. 21:17
  • Herk interprets this as trust built through care for the business, rather than an impressive list of projects or frameworks. 22:18

Communication reflects the quality of thinking

  • Pocock says the strongest developers he has worked with communicate clearly, including readable explanations of what a code change did. This is his observation, not a measured ranking of developer performance. 22:56 23:16
  • Unclear thinking makes it harder both to instruct an agent and to explain what is wrong with its output. Clear terms and boundaries help communicate the client's intent to the agent. 23:16 23:43

Domain-driven design and ubiquitous language

  • Domain-driven design, or DDD, supplies a shared vocabulary: code, developers, clients, and users should use the same terms for the same product concepts. Pocock calls this ubiquitous language. 23:43 24:03
  • His example is an order. Its meaning should remain consistent in code, the database, the UI, and conversations with the client. Refining that meaning helps align the implementation with the requested product. 24:23
  • His Grill with Docs skill extends the interviewing approach to help build this domain vocabulary during the conversation. 24:51