![Nobody Knows What Dave Built [webinar recording]](https://images.squarespace-cdn.com/content/v1/6a7f5f6276258d38aa294d0c/d5e9639f-657d-42b1-917c-a9f8c53a560a/Screenshot+2026-10-09+at+10.55.37+AM.png)
Nobody Knows What Dave Built [webinar recording]
Technical Debt Advisors recently joined the Federal Government Distance Learning Association for a webinar on technical debt, AI, and what happens when organizations become dependent on technology faster than they develop the capacity to understand and maintain it.
Schools Need a Better Way to Think About AI
AI is becoming part of search, writing, software, communications, classrooms, and the systems schools already use. The challenge for schools is no longer whether AI should be allowed. It is how institutions build the judgment, language, governance, and capacity needed to respond as the technology becomes pervasive.
The Guardrails Beneath the Guardrails
In the AI era, organizations can create software faster than ever. Their ability to understand, govern, and maintain it may prove just as important as the speed at which they can build it. That is where technical debt management and cybersecurity begin to overlap, in the shared need to preserve control over systems as they grow more complex.
AI Is Collapsing the Technical Debt Timeline
Since the 1990s, the phrase has brought to mind old systems, accumulated shortcuts, outdated dependencies, thin documentation, and architecture shaped by years of compromise. The debt was something that gathered over time and showed up when a company needed to repair, extend, or replace the software. AI-assisted development brings that debt much closer to the moment the software is created.
You Are Shipping More Code Than Anyone Is Reading
TL;DR: AI can increase software output much faster than it increases your ability to review, test, understand, and maintain what gets produced.
Top 10 Signs Your Employees Are Building Software You Don’t Know About
Because knowing is half the battle.
Top 10 Cultural Habits That Turn AI Coding Into Technical Debt
Because sometimes it’s not just what you do, it’s the way that you do it.
Technical Debt Is Not Just a Technical Problem
TL;DR: Technical debt may live in the code, but it is usually created by business decisions, governance gaps, and company culture.
Congrats, You Have a Dependency Nobody Has Heard Of
TL;DR: If a critical part of your software depends on a tiny project maintained by one stranger on the internet, you should probably know about it.
What Kind of Software Mess Is Your Company?
12 questions. Immediate results. What is your software archetype? And what effect does it have on your business?
As AI coding creates a new class of shadow IT inside ordinary companies, Yet Analytics launches Technical Debt Advisors to help SMBs manage it
As AI coding creates a new class of shadow IT inside ordinary companies, Yet Analytics launches Technical Debt Advisors to help SMBs manage it
How Much Spaghetti Is Too Much Spaghetti?
TL;DR: Spaghetti code becomes a problem when changing one thing regularly breaks three things you did not know were connected.
Your Prototype Has Escaped
TL;DR: If customers, employees, or revenue depend on your prototype, it stopped being a prototype whether you meant it to or not.
Nobody Knows What Dave Built
TL;DR: If your business depends on software that only one employee understands, you have a business continuity problem disguised as an app.