More Giant Robots episodes

623: The AI Paradox: Why Consultants Are Busier Than Ever with Nate Berkopec thumbnail

623: The AI Paradox: Why Consultants Are Busier Than Ever with Nate Berkopec

Published 17 Sept 2026

Duration: 41:19

"LLMs enhance but don't replace human expertise in consulting and software development, with experts leveraging AI for efficiency while maintaining critical judgment and creativity."

Episode Description

Sami talks with Nate Berkopec, owner of Speedshop, about a recent post he made on X and how his business manages to stay ahead of AI and LLMs.Nate str...

Overview

Large Language Models (LLMs) are transforming software development, but they augment rather than replace human expertise. Experts in fields like performance optimization, mathematics, and game design remain indispensable, as their deep domain knowledge allows them to guide AI effectively and achieve superior outcomes. While LLMs can generate code and assist with routine tasks, they lack the contextual understanding, judgment, and creativity required for high-quality, innovative solutions - especially in complex or specialized domains.

The rise of AI has shifted workflows, with developers increasingly relying on LLMs for code generation while facing new challenges in reviewing and verifying AI-produced outputs. Smaller, incremental code changes and strict quality standards are still essential, and human oversight remains critical for ensuring reliability, compliance, and long-term maintainability. Although LLMs accelerate learning and lower entry barriers, true expertise requires more than AI assistance - it demands continuous growth, critical thinking, and the ability to refine and evaluate AI-generated work. As a result, consulting and development continue to depend on human insight, with AI serving as a powerful but supplementary tool.

What If

  • What if you delegated 90% of your code generation to an LLM but enforced strict review rules?

    • Move: Restructure your workflow to generate all code via LLM (e.g., via prompt chaining), then apply a deterministic checklist (max 50 lines/PR, no new dependencies without justification, all functions <10 lines) before merging.
    • Why Now?: LLMs now reliably generate syntactically correct code, but unchecked outputs increase technical debt; small, rule-bound PRs improve review speed and catch edge-case logic errors early.
    • Expected Upside: 30 - 50% faster delivery with lower defect rates, freeing you to focus on architecture and client outcomes instead of typing.
  • What if you positioned yourself as a verifier instead of a coder for AI-generated systems?

    • Move: Offer a "Code Audit + Optimization" service for clients using LLMs, where you review their AI-generated pull requests, identify performance anti-patterns, compliance gaps, and architectural risks using domain-specific checklists.
    • Why Now?: Most solo developers and startups using LLMs lack deep expertise to validate outputs - this creates demand for lightweight, expert validation as a standalone product.
    • Expected Upside: Charge premium hourly or per-PR rates by delivering measurable improvements (e.g., "reduced API latency by 40% post-review"), differentiating from low-cost AI-generated code mills.
  • What if you trained an LLM to enforce your personal coding standards so you never manually review routine changes?

    • Move: Build a fine-tuned LLM or prompt template that automatically reviews your own PRs against strict rules (e.g., method length, test coverage, config consistency), integrating it into your CI/CD pipeline to block non-compliant commits.
    • Why Now?: LLMs can now follow rigid, deterministic rules better than humans in repetitive tasks - this lets you offload mechanical review while preserving quality.
    • Expected Upside: Reclaim 5 - 10 hours/week previously spent on self-review, enabling faster iteration and focus on high-leverage activities like client acquisition or system design.

Takeaway

  • Treat LLMs as force multipliers by first mastering your domain - invest time in deep expertise so AI tools amplify your output rather than replace your thinking.
  • Break all coding tasks into small, vertical slices (e.g., under 100 lines per PR) to improve AI-assisted code review accuracy and maintainability.
  • Use LLMs as tutors, not code generators - force yourself to write code manually after receiving explanations to build real understanding and avoid skill atrophy.
  • Implement strict, automated code quality rules (e.g., linter checks, method length limits) to reduce reliance on subjective human reviews and make AI-assisted validation more effective.
  • Focus consulting or solo offerings on measurable outcomes (e.g., performance metrics, response times) that clients can verify, differentiating your value from generic AI-generated solutions.

Recent Episodes of Giant Robots

10 Sept 2026 622: Six Opinions Wrapped in Code with Kelli Lucas

"Designers and developers must collaborate closely, leveraging AI for efficiency while prioritizing human judgment, ethical alignment, and stakeholder communication to solve complex problems and achieve successful project outcomes."

18 Jun 2026 614: AI Code Audits

AI integration in code development requires human validation and oversight to address trust, quality, and security challenges, with expertise shaping output reliability, strategic trade-offs between speed and technical debt, and ethical considerations like code ownership and trust debt, while emphasizing iterative practices over rigid methodologies.

More Giant Robots episodes