WEB ATELIER (UDIT) Β· Learning by doing, with theory, practice and shared reflection

The Tao of AI Development

URL: https://ruvebal.github.io/web-atelier-udit/methodology/en/tao-of-ai-development/

By RubΓ©n Vega BalbΓ‘s, PhD Β· 2026-01-03

πŸ“‹ Table of Contents


═══════════════════════════════════════════════════════════════════════════════
                              道
                    THE TAO OF AI DEVELOPMENT
                              道
         Ancestral Wisdom for the Age of Machine-Assisted Creation
═══════════════════════════════════════════════════════════════════════════════

β€œThe Tao that can be prompted is not the eternal Tao. The code that can be generated without understanding is not true code.” β€” Lao Tzu, if he had lived to see Stack Overflow


In the ancient scrolls of web development, there exists a sacred text known as β€˜The Tao of the Developer’—a collection of paradoxical wisdom passed down through generations of code warriors. This chapter, dedicated to the art of machine-assisted creation, reveals the eternal truths about AI in the digital realm.


Introduction

These words come from β€œThe Tao of the Developer”, a philosophical guide to the art of web development. This particular collection of wisdom focuses on the sacred path of AI-assisted developmentβ€”a subject that has confounded many a developer and delighted many a user when done with mastery.

The ancient masters of web development understood that AI is not merely a tool, but a force that can either amplify human creativity or trap the developer in a cycle of dependency and ignorance. Through paradox, koan, and practical wisdom, they revealed the path to AI enlightenment.

May these teachings guide you toward the harmonious balance between machine assistance and human understanding, between convenience and craftsmanship.


πŸ“œ The Ancestral Lineage

This collection of wisdom exists within a greater traditionβ€”a pedagogical lineage that traces its roots to the foundational text of computational philosophy: The Tao of Programming, translated by Geoffrey James.

In the evolution of this wisdom tradition, we witness a natural progression:

  1. The Tao of Programming (circa 1980s) β€” The original text, speaking to the universal truths of software development, algorithms, and the relationship between programmer and machine.

  2. The Tao of the Developer β€” The evolution from programming to web development, acknowledging that the modern developer works not only with code but with the web as a medium, balancing technical excellence with user experience, accessibility, and ethical considerations.

  3. The Tao of the Moving Image β€” A specialized chapter, focusing on the sacred path of video in web design, where motion meets meaning, where bandwidth meets beauty, where time itself becomes a design element.

  4. The Tao of AI Development β€” This specialized chapter, focusing on the sacred path of machine-assisted creation, where artificial intelligence meets human wisdom, where generation meets understanding, where the future of human-machine collaboration is written in every prompt, every commit, every choice.


Prologue: The Bargain

β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”
β”‚                                                                              β”‚
β”‚   In the beginning, there was the void.                                      β”‚
β”‚   And the void was without form, and darkness was upon the face             β”‚
β”‚   of the empty repository.                                                   β”‚
β”‚                                                                              β”‚
β”‚   And the Developer said: "Let there be code."                              β”‚
β”‚   And the AI said: "Here is 500 lines. I assume you wanted React."          β”‚
β”‚                                                                              β”‚
β”‚   And the Developer saw the code, and it compiled.                          β”‚
β”‚   But the Developer did not understand it.                                  β”‚
β”‚   And that was the first sin.                                               β”‚
β”‚                                                                              β”‚
β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜

Chapter I: Mephistopheles and the Vibe Coder

β€œAll theory, dear friend, is gray, but the golden tree of life springs ever green.” β€” Mephistopheles to Faust (Goethe, 1808)

Mephistopheles would have loved vibe coding.

The demon who promised Faust infinite knowledge in exchange for his soul now whispers through autocomplete: β€œWhy understand when you can generate? Why learn when you can prompt? Why think when the machine thinks for you?”

The Vibe Coder’s Prayer:

Our AI, who art in the cloud,
Hallucinated be thy name.
Thy tokens come, thy will be done,
On localhost as it is in production.
Give us this day our daily code,
And forgive us our technical debt,
As we forgive those who review our PRs.
Lead us not into documentation,
But deliver us from understanding.
For thine is the context window,
And the parameters, and the training data,
Forever and ever.
Amen.

The Tao responds:

β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”
β”‚                                                                              β”‚
β”‚   The vibe coder asks: "Does it work?"                                      β”‚
β”‚   The craftsman asks: "Why does it work?"                                   β”‚
β”‚   The master asks: "Should it exist at all?"                                β”‚
β”‚                                                                              β”‚
β”‚   Mephistopheles laughs at all three, for he knows:                         β”‚
β”‚   The code that works without understanding                                  β”‚
β”‚   is a loan with compound interest.                                         β”‚
β”‚   The payment comes due at 3 AM on a Friday.                                β”‚
β”‚                                                                              β”‚
β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜

The Three Lies of Vibe Coding

The Lie The Truth The Consequence
β€œIt works, so it’s correct” Compilation is not comprehension The bug you don’t understand will return, with friends
β€œI’ll understand it later” Later never comes Technical debt accrues at 40% APR
β€œThe AI knows best” The AI knows patterns, not your problem You are responsible for code you cannot explain

Chapter II: The Garbage Code Prophecy

β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”
β”‚                                                                              β”‚
β”‚   In the age of infinite generation,                                        β”‚
β”‚   garbage shall multiply like rabbits in spring.                            β”‚
β”‚                                                                              β”‚
β”‚   The repositories shall overflow with:                                     β”‚
β”‚   - Functions that do nothing, eloquently                                   β”‚
β”‚   - Variables named 'data', 'stuff', and 'thing'                           β”‚
β”‚   - Comments that lie with confidence                                       β”‚
β”‚   - Dependencies that depend on dependencies                                β”‚
β”‚     that depend on a single maintainer in Nebraska                          β”‚
β”‚                                                                              β”‚
β”‚   And the graders shall weep.                                               β”‚
β”‚   And the hiring managers shall despair.                                    β”‚
β”‚   And the production servers shall crash at 2 AM.                           β”‚
β”‚                                                                              β”‚
β”‚   This is the Garbage Code Prophecy.                                        β”‚
β”‚   It need not come to pass.                                                 β”‚
β”‚                                                                              β”‚
β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜

The Seven Signs of Garbage Code

  1. The Unnamed Horror: Variables called x, temp, data, thing
  2. The Infinite Scroll: Functions longer than a CVS receipt
  3. The Comment Lie: // This function calculates tax (it does not)
  4. The Dependency Hydra: node_modules larger than the project itself
  5. The Copy-Paste Plague: The same code, slightly different, in 47 places
  6. The Magic Number Cult: if (status === 42) with no explanation
  7. The Dead Code Cemetery: Commented blocks that β€œmight be needed later”

The Antidote

The master said to the student:
"Before you accept AI-generated code, ask three questions:

1. Can I explain this to a junior developer?
   If not, you do not understand it.

2. Can I explain this to my future self at 3 AM?
   If not, you will suffer.

3. Can I explain this to the grader?
   If not, you will fail.

If the answer to any is 'no', you have received garbage.
Garbage in, garbage out.
But you are the filter."

Chapter III: The Craft and the Machine

β€œWrite code for humans first, computers second; the Tao lies in balancing both.” β€” cc-001, The Tao of Development

The machine generates. The human crafts.

Generation is fast, cheap, and abundant. Craft is slow, expensive, and rare.

The future belongs to those who can tell the difference.

The Craftsman’s Oath

I shall not ship code I do not understand.
I shall not blame the AI for my failures.
I shall not hide behind "it compiled."
I shall not sacrifice clarity for cleverness.
I shall not mistake velocity for progress.

I am the human in the loop.
The code is mine to own.
The bugs are mine to fix.
The learning is mine to earn.

The Machine’s Place

β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”
β”‚                                                                              β”‚
β”‚   The AI is:                                                                β”‚
β”‚   βœ… A tireless assistant                                                   β”‚
β”‚   βœ… A pattern library with opinions                                        β”‚
β”‚   βœ… A rubber duck that talks back                                          β”‚
β”‚   βœ… A first draft generator                                                β”‚
β”‚                                                                              β”‚
β”‚   The AI is NOT:                                                            β”‚
β”‚   ❌ A replacement for understanding                                        β”‚
β”‚   ❌ A substitute for experience                                            β”‚
β”‚   ❌ An excuse for not learning                                             β”‚
β”‚   ❌ A scapegoat for bad code                                               β”‚
β”‚                                                                              β”‚
β”‚   The AI does not know your users.                                          β”‚
β”‚   The AI does not know your constraints.                                    β”‚
β”‚   The AI does not know your deadline.                                       β”‚
β”‚   The AI does not know your soul.                                           β”‚
β”‚                                                                              β”‚
β”‚   You do.                                                                   β”‚
β”‚                                                                              β”‚
β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜

Chapter IV: The Ethics of Creation

β€œEvery byte you send travels thousands of miles through cables under oceans. Respect the journey.” β€” img-064, The Tao of Web Images

The Weight of Tokens

Each prompt you send:

  • Consumes energy
  • Generates heat
  • Contributes to carbon emissions
  • Uses water for cooling data centers

The question is not β€œCan AI do this?” The question is β€œShould AI do this?”

β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”
β”‚                                                                              β”‚
β”‚   BEFORE YOU PROMPT, ASK:                                                   β”‚
β”‚                                                                              β”‚
β”‚   β†’ Could I find this in documentation?                                     β”‚
β”‚   β†’ Am I using AI for learning or laziness?                                 β”‚
β”‚   β†’ Is this prompt necessary, or am I procrastinating?                      β”‚
β”‚   β†’ Will I understand the answer?                                           β”‚
β”‚                                                                              β”‚
β”‚   The planet does not have infinite tokens.                                 β”‚
β”‚   Neither does your learning.                                               β”‚
β”‚                                                                              β”‚
β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜

The Human Cost

Behind every AI model:

  • Thousands of human annotators
  • Often in developing countries
  • Often paid poorly
  • Often exposed to harmful content

Your convenience has a supply chain.

The ethical developer acknowledges this. The ethical developer uses AI mindfully.


Chapter V: The Future We Choose

β€œIn shipping, there is learning. In learning, there is growth. In growth, there is the Tao.” β€” wis-003, The Tao of Development

The future of human-machine collaboration is not written.

We are writing it now, with every prompt, every commit, every choice.

Two Futures

Future A: The Garbage Epoch

- Codebases no one understands
- Developers who cannot code without AI
- Systems too complex to maintain
- Knowledge lost to convenience
- The craft, forgotten

Future B: The Augmented Renaissance

- AI amplifies human creativity
- Developers who understand deeply and create broadly
- Systems designed with intention
- Knowledge preserved and shared
- The craft, elevated

Which future do you choose?

The Choice is Daily

Every time you:

  • Copy without understanding β†’ Future A
  • Read, understand, then adapt β†’ Future B

Every time you:

  • Skip the documentation β†’ Future A
  • Write the plan first β†’ Future B

Every time you:

  • Ship without testing β†’ Future A
  • Verify before committing β†’ Future B

Chapter VI: Koans for the AI Age

Koan 1: The Empty Context Window

A student asked the master: β€œMy AI gives wrong answers. What should I do?”

The master replied: β€œDid you give it the right questions?”

The student said: β€œI asked it to fix my code.”

The master said: β€œDid you tell it what your code should do?”

The student was silent.

The master said: β€œThe AI is a mirror. It reflects what you give it. Give it garbage, receive garbage. Give it clarity, receive clarity. The context window is not the AI’s limitationβ€”it is yours.”

Koan 2: The Passing Test

A student celebrated: β€œMaster! All my tests pass!”

The master asked: β€œWhat do your tests test?”

The student said: β€œThat the code works.”

The master asked: β€œWhat does β€˜works’ mean?”

The student said: β€œIt returns the expected output.”

The master asked: β€œExpected by whom?”

The student fell silent.

The master said: β€œA test that passes is not proof of correctness. It is proof that you have not yet imagined the ways it can fail.”

Koan 3: The Confident Hallucination

A student complained: β€œThe AI told me to use leftPad. But leftPad broke the internet in 2016!”

The master smiled: β€œAnd did you check?”

The student said: β€œNo, the AI seemed confident.”

The master said: β€œConfidence is not truth. The AI does not know what it does not know. It speaks with the same tone whether it is correct or hallucinating. Your job is to know the difference. The AI’s confidence is infinite. Your skepticism must match it.”

Koan 4: The Attribution

A student submitted code. The grader asked: β€œDid you write this?”

The student said: β€œThe AI wrote it.”

The grader asked: β€œThen who learned?”

The student said: β€œI learned to prompt.”

The grader said: β€œPrompting is not programming. Understanding is programming. Can you explain this code?”

The student could not.

The grader said: β€œThen you have submitted someone else’s work that you do not understand. This is not learning. This is laundering.”


Chapter VII: The README Covenant

β€œDocumentation unread is documentation unwritten. But documentation unwritten is failure guaranteed.” β€” rrp-011, The Tao of Development

Every repository tells a story. The README is its first chapter.

If you used AI, say so. Clearly. Visibly. Proudly or humblyβ€”but honestly.

The Covenant

## πŸ€– AI Assistance Disclosure

This project was developed with AI assistance.

### What AI Did

- [Specific, honest list]

### What I Did

- [Specific, honest list]

### What I Learned

- [Reflection on the process]

### What I Would Do Differently

- [Growth mindset evidence]

Why this matters:

  1. For you: Forces reflection on what you actually understand
  2. For graders: Allows fair assessment of your learning
  3. For future employers: Shows integrity and self-awareness
  4. For the community: Contributes to honest norms around AI use
  5. For the future: Creates precedent for ethical AI collaboration

Epilogue: The Path Forward

β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”
β”‚                                                                              β”‚
β”‚   The Tao of AI Development is not a set of rules.                          β”‚
β”‚   It is a way of being.                                                     β”‚
β”‚                                                                              β”‚
β”‚   It is the pause before the prompt.                                        β”‚
β”‚   It is the question after the answer.                                      β”‚
β”‚   It is the understanding beneath the code.                                 β”‚
β”‚   It is the ethics above the convenience.                                   β”‚
β”‚                                                                              β”‚
β”‚   The machine will grow more powerful.                                      β”‚
β”‚   The human must grow more wise.                                            β”‚
β”‚                                                                              β”‚
β”‚   This is the path.                                                         β”‚
β”‚   This is the Tao.                                                          β”‚
β”‚                                                                              β”‚
β”‚   道                                                                         β”‚
β”‚                                                                              β”‚
β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜

The Final Warning

β€œDebugging is twice as hard as writing the code in the first place. Therefore, if you write the code as cleverly as possible, you are, by definition, not smart enough to debug it.” β€” Brian Kernighan (and dbg-003)

If the AI writes code you cannot debug, you have not saved time.

You have borrowed time from your future self, with interest.

The debt always comes due.


β€œThe goal is not to replace your thinking with AI, but to amplify your thinking through AIβ€”so that you may build things that matter for a better human living.”


Authorship: RubΓ©n Vega BalbΓ‘s, PhD (UDIT) Β· ORCID: 0000-0001-6862-9081 License: Content CC BY-NC-SA 4.0

Critical Coding for a Better Living.


Source Wisdom
The Tao of Programming The foundational text (Geoffrey James)
The Tao of the Developer (TTOD) The complete wisdom database
The Tao of Moving Images The sacred path of video in web design
AI Practical Guide Practical methodology for AI-assisted development
ACM Code of Ethics Professional ethics guidelines
UNESCO AI Ethics International framework
Faust (Goethe) The original cautionary tale

═══════════════════════════════════════════════════════════════════════════════
                              道
                     END OF THE TAO OF AI DEVELOPMENT
                              道
              May your code be clean and your conscience clear.
═══════════════════════════════════════════════════════════════════════════════