JD sits down with Amanda Nystrom to explore an often-overlooked reality in the tech industry: wellness is not a personal side concern—it’s a performance issue.Drawing parallels between system audits, Postgres health checks, and human behavior, Amanda explains why teams can’t expect long-term reliability, scalability, or high performance if they ignore the health of the people behind the systems. Just as neglected infrastructure leads to outages and technical debt, ignored habits and burnout eventually undermine human performance.This conversation reframes wellness in terms engineers understand: sustainability, performance, and future readiness. If you care about building resilient systems, this episode makes the case for building resilient people, too.

In this episode, Command Prompt Founder Joshua “JD” Drake talks with Andrew Smith, Senior Developer/DBA, about a foundational concept in software engineering that quietly powers modern systems: code generation and single sources of truth.Andrew walks through the evolution of code generation—from early macros and assembly language to modern model-driven architectures—and explains why generating code from a centralized definition is one of the most effective ways to build scalable, maintainable systems. Using practical examples from C, PostgreSQL, and modern frameworks, he breaks down how code generation reduces duplication, prevents drift, and keeps complex systems aligned over time.

Welcome back to More Than a Refresh Presents: T3D Sessions.In this episode, Command Prompt Founder Joshua “JD” Drake talks with Justin Graf, Senior DBA & Engineer at Command Prompt, about a topic every Postgres team needs to understand: why monitoring alone isn’t enough—and why full logging is essential for diagnosing database problems. Justin explains how organizations often rely solely on monitoring tools like PGStatStatements, CloudWatch, or Datadog, without realizing that these tools can’t show query parameters, historical performance shifts, or the root cause behind sudden CPU spikes. Without full logging, teams end up blind during outages, wasting hours trying to detect issues that proper logs would have revealed immediately.