I've spent the past couple of years figuring out how to introduce AI into our engineering organization without breaking things. Or breaking people.
What happens when AI touches production-critical systems? How do you guide thousands of employees without stifling the creativity and speed that makes them effective? And underneath it all, the ethical questions about what we're actually enabling.
I've had countless conversations. Executives worried about staying competitive. Security teams worried about data exposure. Senior engineers who've seen hype cycles come and go. Junior engineers eager to build differently. Artists and product managers with entirely different mental models of what this technology can do.
What I keep running into is a gap.
Some people overestimate AI's capabilities. Others underestimate them, especially the security risks. I work with people who are eager yet complacent - moving fast without understanding what they're exposing. And others who are overly cautious, resistant to change even as the landscape shifts around them.
The real challenge is finding the path between.
How do we adopt AI without treating it as a hammer that will replace everything we've built, including us? How do we implement new technologies with real security risks without exposing critical systems or proprietary data? How do we provide engineers with vetted tools quickly enough that they don't resort to shadow AI - using unapproved tools because we're moving too slowly?
The attack vectors evolve faster than policies can keep up. But locking everything down kills creativity and productivity.
And the scope is massive. Hundreds of engineers developing hundreds of features. Thousands of repositories spanning cloud, hardware, and IoT. Complex partner relationships with their own security constraints. This isn't just a technology problem. It's organizational. Cultural. A test of whether we can adapt without losing what makes us effective.
At some point I realized - this isn't a new challenge.
Every generation faces technologies that move faster than they can comprehend. The printing press. Electricity. The internet. Each brought the same anxieties, the same scramble to adapt, the same fear of being replaced.
I've been thinking about this problem through the lens of Taoism for a while now. Developed in China over 2,500 years ago, Taoism centers on living in harmony with the Tao - the natural flow of the universe. One of its core concepts is Wu Wei, often translated as "effortless action" or "non-forcing."
Wu Wei isn't passivity. It's working with the grain of things rather than against it. Acting deliberately, with purpose, without unnecessary struggle.
The more I sat with this, the more the connection became clear. AI isn't something to fight or fear. It's not something to blindly embrace either. It's a current we need to learn to move with.
Over the past year, these ideas have crystallized into a philosophy for guiding teams through this technology. A technology so powerful that many of us feel paralyzed when it's at our fingertips. At the speed things are changing, we need to move with the current, not against it.
I'm sharing what I've learned here in case it's useful to others navigating similar waters.
The Way of Water
Engineering Principles for the AI Era
The Philosophy
"Nothing in the world is as soft and yielding as water. Yet for dissolving the hard and inflexible, nothing can surpass it." — Tao Te Ching, Chapter 78
Water doesn't force. It finds the path of least resistance, yet reshapes landscapes over time. Not through dramatic acts. Through persistent flow.
Software works the same way. Drops gather into streams. Small code changes accumulate into products. A refactor here, a test there, a cleaner abstraction. None of it feels monumental in the moment.
But the landscape transforms.
We're not trying to move mountains here. We're not rebuilding entire products through vibe coding or replacing teams with AI agents. The goal is simpler - move deliberately, move quickly, and let AI accelerate the drops without bypassing the process. Still small. Still deliberate. But faster and with more purpose.
This isn't about replacing engineers. It's about removing friction so they can focus on the work that actually requires them. The craft doesn't disappear. It becomes more visible.
Core Principles
1. Wu Wei: Effortless Action
"The Tao does nothing, yet leaves nothing undone." — Tao Te Ching, Chapter 37
Wu Wei isn't passivity. It's aligned action. Working with the grain rather than against it.
In practice, this means AI handles the repetitive work - the boilerplate, the already-solved problems, the pattern matching. This frees engineers to focus on what requires human judgment. Architecture decisions. Edge cases. The problems that haven't been named yet.
Let AI draft. You refine. Let AI search. You decide. Let AI suggest. You validate.
The division isn't about replacing judgment. It's about using it where it matters most.
2. The Yielding Strength
"The stiff and unbending is the disciple of death. The soft and yielding is the disciple of life." — Tao Te Ching, Chapter 76
Water yields to obstacles yet wears down stone.
We don't abandon our standards for speed. We let AI amplify our rigor. Code review doesn't disappear - it evolves. Testing doesn't shrink - it deepens.
But rigidity breaks.
I've seen teams cling to processes designed for a world that no longer exists. The process becomes the work instead of enabling it. Standards that refuse to evolve become obstacles, not safeguards.
AI-generated code gets the same scrutiny as human code. Maybe more, because the patterns are less familiar. We're not chasing speed for its own sake. We're building sustainable velocity - the kind that doesn't burn people out.
3. The Empty Vessel
"We shape clay into a pot, but it is the emptiness inside that holds whatever we want." — Tao Te Ching, Chapter 11
The most useful vessel is empty. Ready to receive.
Engineers who hoard knowledge become bottlenecks. Engineers who share discoveries become force multipliers. Your prompt that saved four hours helps the whole team save four hundred.
I've watched this pattern repeat. The engineer who thinks they have all the answers stops learning. The one who thinks they have none stops contributing.
Stay open.
Share what works. Document your AI workflows. Your clever technique is organizational knowledge, not personal advantage. We move faster together than we do in silos.
The knowledge you give away comes back multiplied.
4. Constant Flow, Deep Roots
"The great Tao flows everywhere. All things are born from it, yet it doesn't create them. It pours itself into its work, yet it makes no claim." — Tao Te Ching, Chapter 34
Rivers move continuously yet are fed by deep, patient aquifers.
We experiment constantly. New models, new tools, new patterns. The landscape shifts every few months. What worked last quarter might not work next quarter.
But we stay grounded in engineering fundamentals.
AI changes how we code, not why good architecture matters. It changes how we write tests, not why testing matters. The tools evolve. The principles remain.
Experiment boldly in low-risk contexts. Apply carefully in production. Never stop learning the craft beneath the tools. You can't automate what you don't understand.
5. Knowing Without Possessing
"The Master does his job and then stops. He understands that the universe is forever out of control, and that trying to dominate events goes against the current of the Tao." — Tao Te Ching, Chapter 30
AI output isn't yours to defend. It's raw material to shape.
Don't cling to generated code because it came quickly. Don't resist deleting it because it felt like progress. I've seen engineers spend an hour debugging AI-generated code that would have taken twenty minutes to write from scratch.
Stay light.
Ship what works. Delete what doesn't. The goal is the solution, not the sunk cost. Don't let ego get in the way.
The code doesn't care how it was written.
6. The Uncarved Block (Pu)
"When there is no desire, all things are at peace." — Tao Te Ching, Chapter 37
Pu represents potential before it's shaped. Simplicity. Openness. Beginner's mind.
Approach each AI interaction without preconception. The engineer who "knows" what AI can't do stops discovering what it can. The engineer who "knows" AI will handle everything stops developing their craft.
I've been surprised more times than I can count. Tasks I thought would be trivial turned complex. Tasks I thought would be impossible turned simple.
Stay curious. Stay skeptical.
Both can be true at once.
The Current and the Riverbed
"The best people are like water. Water benefits all things and does not compete with them." — Tao Te Ching, Chapter 8
AI is the current. Fast-moving, powerful, sometimes turbulent.
Engineering discipline is the riverbed. It shapes direction, prevents flooding, ensures the water reaches where it's needed.
Without the current, the riverbed is dry and nothing moves. Without the riverbed, the current scatters and nothing is built.
We need both.
An Invitation, Not a Mandate
"A leader is best when people barely know he exists. When his work is done, his aim fulfilled, they will say: we did it ourselves." — Tao Te Ching, Chapter 17
These principles aren't rules. Water doesn't follow rules. It follows gravity, terrain, the path that opens.
Your context is different from mine. Your constraints, your team, your technology stack, your risk tolerance. What works for a startup looks different from what works in a regulated industry. What works for a team of five looks different from what works for thousands.
Consider this a companion for the journey, not a map.
Take what resonates. Leave what doesn't. Share what you discover along the way.
The way forward is together, in constant motion, navigating by principles that run deeper than the current.