Skip to content

About

Hi, I'm David Hale. I build agents you can trust.

I take the busywork off engineering teams with AI agents, and I build the guardrails that keep a person in charge of what ships. I do it in healthcare, where a bad answer lands on a real patient.

Husband. Father. Code maker. Halestorm.

David Hale

How I got here

I did not start out building software. I started out breaking it. That turned out to be the right order.

  1. 2006 – 2011

    Trevecca Nazarene University

    A degree in Information Technology, and most of my free time in the percussion ensemble, wind ensemble and jazz band. Keeping time for other people turned out to be good practice.

  2. 2012 – 2017

    Breaking software for a living

    I started in QA at Emma, then ThreatQuotient, then LifeWay. Test plans, Selenium grids, API tests, security and accessibility checks. I learned how software fails before I learned how to build it.

  3. 2017 – 2020

    Crossing over

    At LifeWay I moved from testing the product to building it. At Lonely Planet I sat between both worlds, writing the tooling that told teams whether their work held up.

  4. 2020 – 2025

    Healthcare

    EvidenceCare put me inside hospital systems with HL7 FHIR and CDS Hooks. OneStudyTeam and Care Access put me inside clinical trials. This is where I learned the work is never just code.

  5. 2026 – now

    Agents

    At Aeroflow Health I build healthcare agents on Amazon Bedrock and Strands, and the integrations behind them. On my own time I build the guardrails I wish every agent came with.

The full version, with dates and details, is on my resume.

What I believe

  1. Good software is stewardship.

    Every field, status, integration and workflow eventually lands on a real person trying to do their job. The best systems are not just clever. They are understandable and supportable, and they make room for the next person.

  2. Build things that hold up.

    I am less interested than I used to be in looking busy. Software systems, working relationships, family rhythms: I would rather have the ones that last than the ones that demo well.

  3. A person makes the final call.

    An agent can open the pull request. It cannot merge it. I would rather build that discipline into the system than trust my mood on the fifth review of the day.

  4. Respect the conditions.

    You cannot control the weather, force visibility, or pretend things are better than they are. You assess, adjust, and keep moving with the information you have. True on a trail. True in a codebase.

What I'm building

All work

Not on the resume

Latest writing

All posts

Want to talk?

If you are putting agents in front of work that matters and want them to earn it, I would like to hear about it.