Regular Expressions

Ben Griswold and Noah Heldman

Join Noah Heldman and Ben Griswold as they talk about technology consulting and life.

  1. -3 Ч

    Ethical Billing: Time vs. Value in Consulting

    "Billability," "Utilization," "Chargeability." For consultants, these aren't just buzzwords... they are the metrics that often dictate your worth. But is an hour worked always an hour of value? And where is the ethical line when it comes to billing for research, learning, or dealing with slow internal processes? In this episode, Ben Griswold (Grizen) and Noah Heldman (OutcomeSource) unpack the psychological weight of the timesheet. They debate the ethics of billing for "learning on the job," the hidden costs of unnecessary meetings, and why solutioning too early can burn through a budget with zero results. They also dive into a shared frustration: why slow tools like Virtual Desktop Infrastructures (VDIs) act as "handcuffs" for high-performers, destroying flow and value in the process. In This Episode, You'll Learn: The psychological burden of terms like "utilization" and why lawyers might have it worse.The ethics of billing clients for time spent learning new technologies or fixing mistakes.Why "Noah Time" (optimistic estimation) often leads to under-billing.The danger of solutioning too early and how to "measure twice, cut once" to save client budget.Why Virtual Desktop Infrastructures (VDIs) and slow tools kill cognitive flow and project momentum.The argument for investing in your own high-quality tools to maximize value delivery.Connect with Us: Ben Griswold | Grizen: https://grizen.comNoah Heldman | OutcomeSource: https://outcomesource.com

    28 мин.
  2. 14 ФЕВР.

    Vibe Coding vs. Real Engineering: AI As Help, Not Hope

    "Vibe Coding" has become a popular way to describe building software by simply chatting with an LLM. It feels efficient, but it often lacks engineering rigor. In this episode, Ben Griswold (Grizen) and Noah Heldman (OutcomeSource) discuss the difference between this casual approach and "Spec-Based Coding." They share a recent experience using Cursor to build a complex feature. The AI agent got them about 75% of the way there in record time, but when they tested it with a small load, the architecture failed. They had to tear it down and start over. The conversation covers why AI tools often miss non-functional requirements like security rules, database connections, and scaling strategies. Ben and Noah explain why experienced developers are still needed to guide AI agents, essentially acting as mentors to a very fast, but inexperienced, junior engineer. In This Episode, You'll Learn: The definition of Vibe Coding versus Spec-Based Coding.The "75% Illusion" where AI makes a project look nearly finished when the foundation is actually missing.A real-world story about a Firebase function architecture that failed under a minimal load.The specific things AI often forgets to build, such as security rules and pagination.How the role of the senior engineer is shifting toward architectural review and mentoring AI agents.Connect with Us: Ben Griswold | Grizen: https://grizen.comNoah Heldman | OutcomeSource: https://outcomesource.com

    28 мин.
  3. 3 ФЕВР.

    Strong Opinions, Thoughtfully Held, With Dave Holbrook

    What happens when a perfectly designed software system crashes in production because of a single deployment error? You learn the most important lesson in engineering: If you write it, you run it. In this episode, Ben and Noah welcome long-time colleague and technology thought leader Dave Holbrook (CTO at Owner.com). Dave shares his journey from the world of massive enterprises to the fast-paced reality of hyper-growth startups. The trio dives deep into the "unsexy" reality of software architecture...navigating office politics, managing crushing technical debt, and why the goal of "zero tech debt" is a dangerous fantasy. Dave also pulls back the curtain on his daily workflow, revealing how he uses AI agents to write tests, generate specs, and manage tickets, and explains why he believes the unit cost of code is heading to zero. In This Episode, You'll Learn: Enterprise vs. Startup: Why great technical decisions sometimes get overruled by corporate politics (and how to deal with it).The "You Write It, You Run It" Philosophy: A painful story about a memory leak and a DCOM error that changed Dave's career.The Truth About Tech Debt: Why software starts rotting the moment it ships, and how to negotiate pay-down time with leadership.AI in Practice: How Dave uses AI tools (like Cloud Code and Linear) for Test-Driven Development and spec generation.Hot Take: Why "Best Practices" don't exist and the term should be banned.Connect with Us: Ben Griswold | Grizen: https://grizen.comNoah Heldman | OutcomeSource: https://outcomesource.comDave Holbrook on LinkedIn: https://www.linkedin.com/in/davidbholbrook/

    1 ч. 1 мин.
  4. 21 ЯНВ.

    Making a Strategic Bet On The EDGE Operating model

    We all know the problem: a company sets a high-level strategy, but the teams on the ground have no idea how their daily work connects to it. Enter EDGE, a value-driven operating model designed to close that gap. But can a framework built for massive enterprises actually work for smaller teams? In this episode, Ben Griswold (Grizen) and Noah Heldman (OutcomeSource) dive deep into the principles of EDGE: Value-Driven Digital Transformation. Noah breaks down the "Lean Value Tree" using a surprisingly relatable analogy—living to 100 with no health issues—to explain how to connect a 5-year vision to daily initiatives like "cutting sugar" or "walking 6,000 steps." They discuss why "bets" are better than plans, why ROI might be the wrong metric for innovation, and how to implement "Agile Everywhere," even in budgeting and governance. In This Episode, You'll Learn: What EDGE is and why it's more than just another consulting buzzword.The Lean Value Tree explained: Vision -> Goal -> Bet -> Initiative.A practical example of the tree using a personal goal: "Living to 100."Why "bets" are a powerful way to frame strategic risks and avoid the sunk cost fallacy.How to prioritize work using a simple formula: Value / Effort.Why traditional ROI often fails to capture true customer value in digital transformation.Connect with Us: Ben Griswold | Grizen: https://grizen.comNoah Heldman | OutcomeSource: https://outcomesource.com

    50 мин.
  5. 23.12.2025

    Shared Language or Shared Chaos: Why Words Matter

    There are two hard things in computer science: cache invalidation and naming things. In this episode, we tackle the latter. A single word like "integration" or "account" can mean entirely different things to a COO, a salesperson, and an engineer, leading to confusion, rework, and failed projects. The solution? A "ubiquitous language." Join Ben Griswold (Grizen) and Noah Heldman (OutcomeSource) as they dive into the critical, and often overlooked, importance of creating a shared vocabulary across business and technology teams. Drawing on hilarious real-world examples (from "contract contract" in code to a mix-up between "ETL" and "ELT"), they explain why naming things is one of the hardest and most valuable skills in consulting. This is a masterclass in clear communication and the art of getting everyone on the same page. In This Episode, You'll Learn: The real-world confusion caused when a COO hears "integration" and thinks M&A, not APIs.What "Ubiquitous Language" from Domain-Driven Design (DDD) actually means (and why it could have been named better).The hilarious story of a "contract contract" and why clear naming in code is essential.Why engineers should adopt the language of the business, not the other way around.The danger of acronyms: A funny mix-up between ELT (Extract, Load, Transform) and ELT (Executive Leadership Team).Connect with Us: Ben Griswold | Grizen: https://grizen.comNoah Heldman | OutcomeSource: https://outcomesource.com

    25 мин.
  6. 18.11.2025

    The Consultant's Dilemma: Saying No To The Wrong Work

    For any consultant, especially one starting their own firm, the idea of saying "no" to paid work can feel unthinkable. But not all clients are created equal, and taking on the wrong engagement can be far more costly than turning it down. How do you spot the red flags of a toxic environment, avoid burnout, and know when to walk away? In this episode, Ben Griswold (Grizen) and Noah Heldman (OutcomeSource) tackle the difficult but essential art of saying no. They explore the key reasons to decline work, from toxic cultures and value misalignment to simple burnout. Highlighting their own complementary "starter vs. finisher" and "yes vs. no" personalities, they share a hilarious and cautionary tale of a client who scrutinized a 1,000-line estimate quarter-hour by quarter-hour—a defining moment in learning when an engagement is doomed from the start. In This Episode, You'll Learn: Why a toxic client environment is the #1 reason to say no, and how it impacts more than just your work.How to balance taking on necessary work with staying true to your personal and professional satisfaction.The danger of the "sunk cost fallacy" in long client pursuits.A hilarious cautionary tale about providing too much detail in an estimate and the micromanagement that followed.How to respect personal values when deciding which clients to work with.Connect with Us: Ben Griswold | Grizen: https://grizen.comNoah Heldman | OutcomeSource: https://outcomesource.com

    28 мин.

Оценки и отзывы

5
из 5
Оценок: 4

Об этом подкасте

Join Noah Heldman and Ben Griswold as they talk about technology consulting and life.