Tech Council

Tech Council

By Duncan MapesNewsTechnologyTech News
Download on the App Store

Tech Council episodes

  • Engineering Leaders vs Tech Debt: A Realistic Conversation | Episode 28

    Tech debt exists at the intersection of engineering, business incentives, and system architecture. In complex organizations, it becomes a multidimensional problem involving operational risk, system reliability, long-term scalability, and developer productivity. 

    In this analytically grounded episode, Duncan and Jason dissect tech debt through the lens of system thinking.

    They introduce a working model for categorizing tech debt into functional, structural, and data-related risk, explaining how each impacts throughput, incident frequency, and time-to-recovery. They also examine how vulnerabilities and poor data contracts masquerade as “bugs” but are often symptoms of deeper architectural debt. 

    The conversation presents a practical playbook for leaders: how to assess tech debt, measure its economic impact, define acceptable thresholds, and integrate it into strategic planning.


    Top Takeaways:

    • Tech debt can be defined in various ways depending on context.
    • Shortcuts taken to meet business needs contribute to tech debt.
    • Tech debt is not just about code quality but also about business outcomes.
    • Standards change over time, leading to new tech debt.
    • Quantifying tech debt is essential for effective management.
    • Managing tech debt requires strategic planning and documentation.
    • Business leaders need to understand the implications of tech debt.
    • Justifying tech debt investments is a common challenge.
    • Effective communication with business partners is crucial for tech debt management.
    • A structured approach to documenting tech debt can aid in prioritization.


    Connect with us:

    Duncan Mapes

    DevGrid.io

    DevGrid on LinkedIn

    DevGrid on X

    39 min
  • Platform Engineering Playbook: Autonomy + Standards | Episode 27

    Most engineering failures can be traced back to two weak points: unclear standards or excessive autonomy. This episode presents a structured examination of how platform engineering resolves this tension to create resilient systems.

    Duncan and Jason break down the cause-and-effect chains behind incidents: data inconsistencies, missing resiliency patterns, queue backlogs, or unplanned API dependencies. They argue that resilient systems emerge from predictable inputs like, consistent data contracts, reliable backfill strategies, upstream validation, and well-defined ownership boundaries.

    This episode provides a mental model for designing platforms where autonomy accelerates delivery, while standards protect system health. It highlights the value of pre-incident thinking and gives a blueprint for building platforms that remain operable even under load, failure, or organizational drift.


    Top Takeaways:

    • Automation is essential for effective platform engineering.
    • Balancing enablement and independence is crucial for user adoption.
    • Self-service capabilities enhance scalability and efficiency.
    • Evangelizing the platform can drive user engagement and adoption.
    • Creating friction can reduce unnecessary support requests.
    • Manual reviews should be a temporary solution, not a permanent process.
    • Setting clear standards and guidelines is vital for platform integrity.
    • Building a culture of support fosters better relationships with users.
    • Understanding user needs helps in creating effective platform solutions.
    • Empowering key individuals can enhance platform adoption across teams.


    Connect with us:

    Duncan Mapes

    DevGrid.io

    DevGrid on LinkedIn

    DevGrid on X

    36 min
  • How to Build Resilient Systems in Complex Enterprises | Episode 26

    When systems fail, it’s rarely because no one saw it coming. It’s because no one planned for it. 

    In this episode, Duncan Mapes and Jason Ehmke share real-world lessons from years of building and scaling technology across enterprise environments where downtime costs dollars.

    They explore the art of designing resilient systems that can withstand inevitable failure points, recover quickly, and continue operating under pressure. From team culture to proactive design checklists, this conversation dives into how engineering leaders can turn system reliability into a competitive advantage.

    Top Takeaways:

    • Designing for failure is crucial in system architecture.
    • Understanding failure points is essential for system resiliency.
    • Resiliency can mean different things depending on the context.
    • Asking the right questions during project kickoff is vital.
    • Complex enterprise environments have unique challenges.
    • Responsibility for failures should not be shifted to others.
    • Handling app stability is a core responsibility of developers.
    • Everything in a system can fail at some point.
    • Evaluating business impact is crucial for prioritizing resiliency efforts.
    • Creating a resiliency checklist can guide design and implementation.


    Connect with us:

    Duncan Mapes

    DevGrid.io

    DevGrid on LinkedIn

    DevGrid on X

    36 min
  • Stop Wasting Money on Conferences — Do This Instead | Episode 25

    Every year, companies spend thousands sending their engineers to conferences. 

    Flights. Hotels. Per diems. All in the hope of “learning” and “networking.” But when they return? The notebooks gather dust, and the insights never leave their laptops.

    In this episode of Tech Council, Duncan Mapes and Jason Ehmke pull back the curtain on what actually makes conferences worth attending. From understanding why you’re going, to choosing who should go, to how that knowledge is shared afterward, they uncover the strategies that separate teams who grow from teams who just take selfies at the expo hall.

    They also explore local meetups to internal learning sessions that often yield more value for less cost.

    If you’ve ever wondered whether conferences are worth the budget line item, this episode gives you the framework to find out.


    Top Takeaways:

    • Conferences can provide valuable learning opportunities for engineers.
    • Networking at conferences often yields more insights than formal sessions.
    • Local meetups can be just as beneficial as large conferences.
    • Budgeting for conferences requires careful consideration of ROI.
    • Selecting attendees for conferences can be a challenging process.
    • Knowledge transfer after conferences is crucial for team growth.
    • Encouraging participation in local events fosters community engagement.
    • Engineers should aspire to share knowledge through talks at meetups.
    • The tech industry is constantly evolving, making continuous learning essential.
    • Feedback from the community can enhance future discussions on conference attendance.


    Connect with us:

    Duncan Mapes

    DevGrid.io

    DevGrid on LinkedIn

    DevGrid on X

    25 min
  • Top Book Recommendations for Tech Professionals and Engineering Managers | Episode 24

    Every great leader has a few books that quietly shaped how they lead.

    For Duncan and Jason, those books go far beyond tech manuals. They’re the ones that teach you how to think, how to communicate, and how to take responsibility when things get hard.

    In this week’s Tech Council, they open their personal libraries and share the titles that stuck. Expect reflections on ownership, transparency, and the hidden leadership lessons inside biographies, history books, and even fiction.

    This isn’t your ordinary book recommendations episode. It’s about why some ideas endure, why others fail in practice, and why the best tech lessons sometimes come from outside of tech entirely.


    Books Mentioned in this Episode:

    • The Scaling Era: An Oral History of AI
    • Extreme Ownership: How U.S. Navy SEALs Lead and Win
    • The Dichotomy of Leadership
    • Radical Candor
    • Turn the Ship Around
    • PHP/MySQL Programming for the Absolute Beginner
    • The Innovators: How a Group of Hackers, Geniuses, and Geeks Created the Digital Revolution
    • John Adams by David McCullough
    • 1776 by David McCullough
    • The Daily Stoic: 366 Meditations on Wisdom, Perseverance, and the Art of Living
    • Good to Great: A Study of Management Strategies of Companies with Lasting Growth
    • High Output Management by Andy Grove
    • 12 Rules for Life: An Antidote to Chaos
    • The Hard Thing About Hard Things
    • What You Do Is Who You Are: How to Create Your Business Culture
    • Rework by Jason Fried and DHH
    • High Growth Handbook
    • Three-Body Problem
    • The Alchemist

    Connect with us:

    Duncan Mapes

    DevGrid.io

    DevGrid on LinkedIn

    DevGrid on X

    35 min
  • Habits That Make or Break Hybrid Teams | Episode 23

    The hybrid workplace has become the defining experiment of modern engineering, and most leaders are still figuring it out.

    In this Tech Council episode, Duncan Mapes and Jason Ehmke analyze the habits that drive high-performing hybrid teams. They discuss proximity bias, performance evaluation, and how communication systems shape fairness and culture.

    They dissect the bad habits that derail trust (like reactive communication and lack of structure) and the good ones that strengthen it (like clear metrics, empathy, and visibility).

    Whether you’re leading across time zones or transitioning from in-office to hybrid, this episode offers actionable insights drawn from years of managing distributed engineering teams.


    Top Takeaways:

    • Hybrid work can create feelings of exclusion among remote employees.
    • Intentional communication is crucial in remote settings.
    • Establishing clear norms helps teams function effectively.
    • Performance management in hybrid environments requires careful consideration.
    • Promoting remote employees can be challenging due to visibility issues.
    • Building relationships is essential for team cohesion.
    • Junior employees need guidance to develop professional skills remotely.
    • Regular check-ins can help maintain team engagement.
    • Documentation of achievements is vital for remote employees.
    • Creating opportunities for in-person interactions can enhance team dynamics.


    Connect with us:

    Duncan Mapes

    DevGrid.io

    DevGrid on LinkedIn

    DevGrid on X

    48 min
  • The ONLY Way App Managers Can Balance Velocity and Stability | Episode 22

    Let’s be real: app managers are stuck in the middle. On one side, business leaders want features yesterday. On the other, teams struggle under mounting tech debt.

    Duncan Mapes and Jason Ehmke break down the complex challenges app managers face in balancing velocity and technical debt. They explore how technical advocacy, stakeholder trust, and long-term business alignment converge to shape outcomes.

    They highlight how trust, advocacy, and smart decision-making can turn impossible situations into opportunities for innovation.


    Top Takeaways:

    • Balancing velocity and tech debt is crucial for app managers.
    • There is no one-size-fits-all approach to managing tech debt.
    • Building strong partnerships with business leaders is essential.
    • Tech debt should be intertwined with business strategy.
    • Continuous improvement requires measuring success and outcomes.
    • App managers must advocate for necessary tech changes.
    • Justifying technical decisions is key to gaining support.
    • Encouraging innovation can lead to valuable insights.
    • Effective communication is vital in stakeholder conversations.
    • Understanding the business impact of tech decisions is critical.


    Connect with us:

    Duncan Mapes

    DevGrid.io

    DevGrid on LinkedIn

    DevGrid on X

    34 min
  • Talent Acquisition in Tech: What Companies Get Wrong | Episode 21

    Every great product starts with people. But finding the right people, and keeping them, has become one of the hardest challenges in tech.

    In this episode, Jason Ehmke and Duncan Mapes unpack the hidden struggles of talent acquisition. From navigating contract-to-hire strategies to cultivating trust through transparency, they share real-world lessons from building engineering teams that last. 

    Beyond résumés and interviews, the conversation dives into how leadership directly shapes retention, why recruiters are more than gatekeepers, and how slow, clunky processes quietly repel top talent. 

    This episode is about balancing short-term hiring pressure with the long game of building resilient, high-performing teams.


    Top Takeaways:

    • Hiring the right people is crucial for success.
    • Talent acquisition should be a thoughtful process.
    • Contract-to-hire can mitigate hiring risks.
    • Leadership quality directly impacts team performance.
    • Creating opportunities for lateral mobility retains talent.
    • Transparency fosters trust within teams.
    • Building relationships with recruiters enhances candidate quality.
    • Streamlining recruitment processes saves time and resources.
    • A positive team environment encourages retention.
    • Balancing short-term needs with long-term goals is essential.


    Connect with us:

    Duncan Mapes

    DevGrid.io

    DevGrid on LinkedIn

    DevGrid on X

    47 min
  • Six Pillars of a Mature API Practice | Episode 20

    APIs are everywhere, but maturity in API practices is rare.

    Buying a gateway doesn’t mean you have an API strategy. What matters is governance, security, and making life easier for developers who build and consume those APIs. 

    In this episode, Duncan and Jason unpack the real challenges behind building a sustainable API practice: how to avoid sprawl, how to strike the balance between control and flexibility, and how to embed security into every layer. 

    They also share lessons on centralizing API governance without killing innovation, and why the best APIs put developer experience at the core.


    Top Takeaways:

    • API gateways have become essential in modern architecture.
    • The interpretation of API gateways varies among teams.
    • A mature API practice requires standards and governance.
    • Security is a primary benefit of using API gateways.
    • Developer experience is crucial for API adoption.
    • Centralized governance helps manage API inventory effectively.
    • API Gateway solutions vary in capabilities and deployment models.
    • Automation can streamline API deployment processes.
    • Collaboration between teams is necessary for API success.
    • Documentation and onboarding processes impact developer engagement.


    Connect with us:

    Duncan Mapes

    DevGrid.io

    DevGrid on LinkedIn

    DevGrid on X

    32 min
  • What Is SRE? Site Reliability Engineering Explained | Episode 19

    Most companies are doing SRE wrong.

    Hiring SREs doesn’t make you reliable. Metrics dashboards don’t guarantee accountability. And cultural change doesn’t happen because you wrote it on a slide deck.

    In this episode, Duncan Mapes and Jason Ehmke push back against the misconceptions. They argue that SRE isn’t a bolt-on team but a systemic shift in how engineering works. Without shared accountability, meaningful metrics, and cultural buy-in, SRE will fail. 

    And no, copying Google’s model isn’t the answer.

    If you think SRE is just a headcount play, this episode will challenge everything you believe. Got a different perspective? Drop us a review, share your comments, and send your toughest SRE questions our way.


    Top Takeaways:

    • SRE is a complex practice that varies across organizations.
    • Defining SRE upfront can prevent chaos later.
    • SRE is not just about taking over responsibilities; it's about collaboration.
    • The role of SREs is to guide and support application teams.
    • Key metrics for SRE success include mean time to detect and restore.
    • Cultural transformation is essential for successful SRE implementation.
    • Finding early wins can help demonstrate the value of SRE.
    • Effective communication is crucial for SREs to succeed.
    • SRE teams should focus on toil reduction and automation.
    • Building a strong relationship between SREs and app teams is vital.


    Mentioned in this Episode:
    Site Reliability Engineering: How Google Runs Production Systems - https://www.oreilly.com/library/view/site-reliability-engineering/9781491929117/

    Connect with us:

    Duncan Mapes

    DevGrid.io

    DevGrid on LinkedIn

    DevGrid on X

    45 min

About Tech Council

From the publisher's feed

Are you a tech leader, architect, or engineer navigating the intricacies of building within the enterprise? Tech Council delivers the strategies and insights you need to succeed. Hosted by Duncan…