Skip to content
PodSubs
ShowsPeopleGuestsJobsNewsEvents
More
BlogPodCred
Menu
ShowsPeopleGuestsJobsNewsEventsBlogPodCredNetworksSign in
Join nowSign in
  • Shows
  • People
  • Jobs
  • News
  • More
    • Guests
    • Events
    • Blog
    • PodCred
    • Networks
    Join nowSign in

The 365 Commitment

The 365 Commitment artwork

Day 337 - Principle Artifact Confusion

Sep 11, 20266 minAudio

I was speaking with someone who might have literally had stars in their eyes. He was glowing with enthusiasm over his newfound ability to develop complex software using an AI Coding tool. He waxed prophetic, predicting the immediate death of the software development world as we know it. This new technology was a revolution, and pretty soon, even my grandmother will be vibe coding her own SAAS tools. I could not help it; I immediately made a connection in my mind to the Nike Free movement circa 2004. You might remember this, especially if you are a runner. The hype around barefoot running was everywhere, due in large part to a few books that were written on the subject of long-distance runners from indigenous tribes that did remarkably well with minimalist footwear. I remember almost the exact conversation I had about AI coding, but in this situation the starry-eyed young man was talking about his new Vibram FiveFingers shoes. I am sure you remember these: the gloves you would put on your feet and run around in them. In 2001, Nike designer Tobie Hatfield and other members of Nike’s innovation team visited Stanford and watched coach Vin Lananna’s track athletes running barefoot on the grass. Hatfield asked why. Lananna told him he believed the practice gradually strengthened the athletes’ feet, made them less injury-prone, and therefore allowed them to tolerate more training. Hatfield later described that as Nike’s “aha moment.” See reference article here: https://www.designboom.com/design/tobie-hatfield-nike-free-interview-03-19-2014/ There is an important distinction here. The key concept is gradual. Lananna was not apparently telling his athletes, “Shoes are bad, throw them away.” This also was not a new concept. Barefoot running and minimalist training had existed among serious runners for decades. There was a key principle at play: Don't let the equipment do so much work that the body loses the ability to do the work itself. The principle being deployed by the Stanford running team is analogous to a team of expert software developers that start to incorporate new AI coding tools into their practice. The Stanford practice might have been: normal training + carefully dosed barefoot work + soft surface + conditioned elite athletes + coaching supervision. Unfortunately, Nike's big moment became the following: Natural running is better. Buy these shoes and run naturally. Now, in Nike's defense, they had actually built progression into the advertising. They created a free number scale which would help you to slowly migrate from conventional shoes to progression toward barefoot. This is not what happened. The same way no one really buys all the Gatorade drinks for pre-, during-, and post-workouts either. The result was disastrous. A runner who spent 20 years running in conventional shoes had muscles, tendons, and movement patterns adapted accordingly. Put that running suddenly into a flexible, low-drop shoe, and suddenly you are changing where the stress occurs. The injury data that poured in was not good. What Stanford had learned is that the human foot benefits from being strong and allowed to move. That knowledge became a conclusion held by the running community that cushioning, support, conventional shoes, and existing training principles are wrong. We have the same phenomenon happening with AI coding tools today. Experienced engineers use things like abstraction, modularity, tests, source control, code review, architectural boundaries, debugging discipline, and iterative development. AI coding tools observe and automate fragments of those practices. Then the industry starts behaving as though the tool itself has replaced the need for the underlying engineering discipline. AI can automate parts of software engineering. The danger begins when we mistake those automated parts for software engineering itself. Principle-Artifact Confusion occurs when a sophisticated practice is reduced to one visible component; that component is productized, and eventually the product is mistaken for the principle that made the original practice successful. When new technology arrives, there is a tendency to abandon basic principles far too quickly. Novelty makes us believe the old rules no longer apply. We invent new terminology, new processes, new organizational structures, and sometimes entirely new philosophies for problems we already know how to solve. AI does not eliminate the fundamentals of running a good business. Good data still matters. Clear ownership still matters. Security still matters. Customers still matter. Measuring outcomes still matters. Good management still matters. A bad process does not become a good process simply because an AI agent is performing it. Before asking what AI can change, make sure the underlying business principles are sound. Technology should amplify good fundamentals, not provide an excuse to abandon them.

Audio and video play straight from the show's own hosting. PodSubs stores and serves no media.

Transcript

From the show.

This is day. 337. principal artifact confusion of a speaking with someone who might have literally had stars in their eyes. He was glowing with enthusiasm over his Newfound ability to develop complex software using an AI coding tool. He waxed prophetic predicting the immediate death of the software development world as we know it. This new technology was a revolution and pretty soon even my grandmother will be Vibe coding her own SAS tools. I could not help it. I immediately made a connection to my mind to the Nike free movement Circa 2004 you might remember this especially if you are a runner the hype around barefoot running was everywhere due in large part to a few books that were written on the subject of long distance Runners from indigenous tribes that did remarkably well with minimalist Footwear. I remember almost the exact conversation I had about AI code I had about a adding but in this situation The Starry Eyed young man was talking about his new Vibram Five Finger shoes. I'm sure you remember these shoes the gloves that you would put on your feet and run around in them. In 2001 Nike designer tobie Hatfield and other members of the Nike Innovation team visited Stanford and watched code vinyl's track athletes running Barefoot on the grass. Hatfield asked why lanata told him that he believed the practice gradually strengthened The Athlete's Feet made them less injury-prone and therefore allowed them to tolerate more training. Hatfield later described that as Nikes aha moment. There's an important distinction here though. The key Concept in the training was gradual. Lenana was not apparently telling his athletes shoes are bad throw them away. This also was not a concept. This also was not a New Concept. barefoot running and minimalist training had existed among serious Runners for decades There was a key principle at play. Don't let the equipment do so much work that the body loses the ability to do the work itself. The principle being deployed by the Stanford running team is an anal is analogous to a team of expert software developers to start to incorporate new AI coding tools into the practice. The Stanford practice might have been normal training plus carefully carefully dosed Barefoot work on soft surfaces with conditioned athletes under coaching supervision. Unfortunately Nikes big moment became the following natural running is better buy these shoes and run naturally. Now a Nike is the fence they had actually built progression into their advertising. They created a free number scale that would help you slowly migrate from conventional shoes to toward and progress towards Barefoot. This is not what happened though the same this is the same reason why nobody actually buys the Gatorade Gatorade drinks for pre. during and post workouts either the result from Nike's campaign was disastrous a runner who spent 20 years in conventional shoes had muscles tendons movement patterns adapted accordingly put that Runner suddenly into a flexible low Drop shoe. And suddenly you were changing where the stress occurs the injury data that poured in was not good. What Stanford had learned is that the human foot benefits from being strong and allowed to move that knowledge became a conclusion held by the running community that cushioning support conventional shoes and existing training principles are wrong. We have the same phenomenon happening today with AI coding tools. Experienced Engineers use things like abstraction modularity tests Source control code review architectural boundaries debugging discipline iterative development AI coding tools observe an automate fragments those practices, but not the entire thing. Then the the industry starts behaving as though the tool itself has replaced the need for all these underlying engineering disciplines. AI can automate parts of the software engineering process certainly the danger begins when we mistake those automated parts for software engineering itself. I call this principle artifact confusion and this occurs when a sophisticated practice is reduced to one visible component that component is then productized and eventually the product is mistaken for the principal that made the original practice successful. When new technology arrives, there is a tendency to abandon basic principles far too quickly. Novelty makes us believe that the old rules no longer apply. We invent new terminology new processes new org structures and sometimes entirely new philosophies for problems. We already know how to solve. AI does not eliminate the fundamentals of running a good business good data still matters clear ownership still matters security still matters customers still matter measuring your outcomes absolutely matter and good management is still a thing a bad process does not become a good process simply because an AI agent is performing it. Before we before asking what AI can change make sure that the underlying business principles are sound technology should amplify good fundamentals not provide an excuse to abandon them all together.

Open the transcript file

Hosts and Guests

Nobody is credited on this episode yet.

Credit the people on this episode

Be the first to rate this episode

More episodes

All episodes
  1. Day 3,239 - Your Minimum is Your Faith

    Nov 20, 20262 minAudio

    I have been thinking lately about the relationship between faith and the amount of effort we are willing to contribute toward something we want to become. We all have ambitions of one kind or another. Perhaps we want to...

    Credit the people on this episode

  2. Day 3,238 - Understanding Action Crisis

    Nov 18, 20265 minAudio

    A fascinating psychological process occurs when a person moves from believing they can accomplish something to recognizing they cannot. I have been here several times, both in physical challenges and mental ones. I have...

    Credit the people on this episode

  3. Day 3,237 - Jedi Physiological Tricks

    Nov 17, 20264 minAudio

    This morning around 2 a.m., one of my dogs started to make a commotion downstairs. He was whining, barking, carrying on. Of course, I am the one that gets to deal with this sort of thing, so I go downstairs and find my...

    Credit the people on this episode

  4. Day 3,236 - Separating the Dream from The Decision

    Nov 17, 20263 minAudio

    I have noticed a weird phenomenon about me. I get myself sold on something awesome, or at least the idea of something awesome. In my mind, the dream and ambition of it sound great, and I start thinking of all the...

    Credit the people on this episode

  5. Day 3,235 - Learning to Rest

    Nov 15, 20263 minAudio

    So when you are actually tired. Meaning that you legitimately need a break. Not because you are just feeling down, anxious, depressed, or for some other reason, but when you are just worn out, how do you deal with that?...

    Credit the people on this episode