The Tech Trek

There are a handful of genuinely useful practitioner observations - the bottleneck-inversion argument (velocity creates downstream pile-ups) and the skills-gap risk for junior engineers are worth hearing - but much of the episode is generic AI-enthusiasm filler and mutual agreement rather than dense, novel claims per minute.

“we have some teams that are orchestrators that are managing agents and orchestrating those agents from requirements all the way to deployment”

“if we don't start solving for them now, we're going to all of a sudden have all this, our cycle times are going to reduce. We're going to have a whole bunch of code just waiting to ship”

The bottleneck-inversion framing (more code velocity exposes downstream QA/deployment constraints) is a genuinely non-obvious point, and the concern that an all-principal-engineer model creates a junior skills pipeline gap is underexplored elsewhere - but the dominant framing of 'AI as accelerator not replacement' and the orchestrator concept are now universal talking points.

“How do you become an orchestrator of this versus an operator?”

“if we are going to go and look at code as easy to produce, are we shifting where we are hiring from that side to potentially a little bit downstream?”

Kevin Haggard is a legitimate VP of Engineering at a real mid-market cybersecurity company speaking from hands-on implementation experience - AI Dev Days, gateway architecture, team-level adoption variance - which is practitioner substance; docked for not being at hyper-scale and for offering relatively few hard-won surprises.

“we do have basically like an AI gateway or proxy that allows us to only access certain LLMs through our various partners”

“we've had them come in, help us do training sessions broadly for the whole organization. and with engineering, that includes product and design”

A handful of concrete examples land well - Word docs to Jira tickets in minutes, prototype to working front-end in hours, named partner roster (Microsoft, AWS, Anthropic, Atlassian) - but the episode contains zero hard metrics, no adoption percentages, no cost figures, and outcomes are described qualitatively rather than measured.

“we have some of our product managers take word documents and that turned into jira tickets within hour with all uh with well actually within a few minutes with a lot of fidelity”

“going from that prototype to actually having working front end code tied to the APIs connected up, just took hours instead of days and weeks”

The host defaults to 'Absolutely,' 'Fantastic,' and '100%' after nearly every answer, introduces lengthy personal opinions mid-question that dilute the guest's airtime, and never challenges a single claim - resulting in an agreeable PR-adjacent chat rather than a probing interview.

“Absolutely. All right, before we start, Barracuda, what do you guys do?”

“I'm a big believer that those that are trying to cut headcount by AI will have bigger problems than those that are embracing it to bring efficiency to teams”