The engines are purring. The Atlantic is glass. You are three hours out of Miami, pointed toward Bimini, and everything is perfect until your old academy roommate asks the question.
Steve asks when you are actually going to use artificial intelligence to build something.
You are standing at the helm of your sixty-two foot weekender. Your boat. Your friends are below deck. You have the conn. You know exactly where you are, where you are going, and how to get there. You have earned the right to these weekend runs to the Bahamas. Coast Guard Academy. Eight years of service. You can navigate by stars if the electronics fail.
Steve, your academy roommate, is sprawled across the fighting chair with a beer, looking entirely too relaxed for someone who just closed a Series C for his artificial intelligence powered accounting software startup. He was always like this. Comfortable asking uncomfortable questions. Lucky too. After graduation, you got stationed in the Caribbean doing actual Coast Guard work while Steve somehow pulled Lake Michigan. Spent his summers sailing and winters holed up in the barracks working on his Master of Science in Computer Science. You used to give him endless grief about it. Now he is giving you grief about AI.
You say that you have been reading about it. You talked to your vendor partners. You are evaluating options.
Steve asks if you bought a book on nuclear submarines. He says that is what you are doing. You are trying to read your way into understanding how nuclear submarines work. But you are a surface vessel guy. Two dimensions. Combustion engines. You cannot just read about going three-dimensional and atomic. It does not work that way.
You throttle back slightly. He has your attention. You tell him you run a software company and do not have time to play with every new tool that comes along.
Steve reminds you that you toured three datacenters before you picked your hyperscaler. You flew to Seattle, Northern Virginia, and Dublin. You met their executive teams. You smelled the diesel in the tanks. You looked at the log books of the Caterpillar generators. You asked about redundancy and cooling systems. You wanted to see the actual infrastructure.
You argue that was different. That was critical infrastructure.
Steve asks if AI is not. He sits up now. He explains his company has six engineers. Two of them are Certified Public Accountants who learned to code last year. Four are recent graduates. They are eating market share from competitors with fifty-person engineering teams. He asks if you want to know why.
You do, actually.
Steve says it is because his competitors are still building like it is twenty twenty. They are running two-week sprints and arguing about story points while his two Certified Public Accountants are shipping features because they understand the accounting domain and AI handles the parts they do not know yet.
The boat settles into the new speed. You have another hour before you need to navigate the approach to Bimini. Plenty of time for this conversation you have been avoiding. You tell him you know how to code and that you still write code.
Steve asks when the last time you shipped something was. It is longer than you want to admit.
The bottom line is simple. If you are a Chief Technology Officer who still writes code, you need to stop reading about AI infrastructure and start building with it. Not because it makes for good leadership theater. Because you literally cannot understand what is changing without hands-on experience.
The literacy problem is real. Your mental models for estimation, code review, testing, and deployment are all calibrated for human developers working at human speeds with human constraints. AI agents operate under completely different physics. You cannot read your way out of this gap.
Think about your first software job after the academy. Sure, you had watched Office Space. But that movie did not teach you what it actually meant to be a developer. What taught you was the late hours debugging production incidents. The peculiar satisfaction of solving interesting problems buried in terrible codebases. The accumulated scar tissue from shipping code that mattered. Those experiences formed your entire point of view on software development. That foundational understanding is what got you to the leadership position you are in today.
Or think about this boat. You did not buy it based on the brochure. You sea-trialed it. Twice. You brought your own captain to check the systems. You ran it hard to see how it handled. You did not read your way into those decisions. You lived them.
AI-assisted development is a larger shift. And you are the Chief Technology Officer. You do not get to delegate understanding the primary AI Infrastructure your organization uses to build software.
You need to understand what getting your hands dirty actually means. Steve asks what you would actually do. He tells you to pull a story card. Real work. Something that matters but will not sink the company if you experiment on it. Work it all the way through to release using AI assistance. Do not block off Friday afternoon for three hours and declare victory. Own the entire lifecycle.
You are probably thinking exactly what Steve just called out. Friday afternoon. Three hours with the tools. Make a decision. Move on. That is not enough.
You need to experience what changes when you can generate entire modules from specifications instead of functions from partial lines. How code review shifts when you are validating agent output instead of human reasoning. What testing means when the thing writing the code can also generate comprehensive test suites. Where the new bottlenecks actually are in the workflow.
The knowledge you need exists in the delta between your expectations and reality. You can only get it from the surprise of discovering your assumptions were wrong.
The competitive reality is stark. Steve takes another pull from his beer and says his competitors have bigger teams. Better funded. More mature processes. They have architects and principal engineers and whole departments dedicated to quality assurance. And they are losing ground to two Certified Public Accountants and four kids fresh out of college.
You say it is because they are using AI.
Steve says it is because they are still building like it is twenty twenty and his team is not. They are optimizing for constraints that do not exist anymore when you are working with AI agents. They are running story pointing sessions for work that does not get measured in story points. They are doing code reviews designed for human cognitive limits when the thing that wrote the code does not have human cognitive limits.
He leans forward. He says they all know about AI. They are all evaluating it. They have some pilot program running in a corner somewhere. But they are not reorganizing around it. They are trying to bolt AI onto their twenty twenty processes and wondering why it is not transformative.
The gap is being exploited by people like Steve. The guy who spent his Coast Guard winters in a Lake Michigan barracks writing code for his master's degree. That same guy now runs circles around established software companies with two Certified Public Accountants and some recent graduates.
Then there is the authority problem. You tell Steve that you hear a lot about developers being happy. Retention is good. The team likes the processes. You ask why you should rock the boat.
Steve actually laughs at that. He says a happy crew is a good crew. He is not disputing that. But you are the captain. You do not get to delegate this decision to your crew based on whether they are comfortable.
He gestures at the helm. He asks if you take a vote when you are navigating into Bimini and the weather changes. He asks if you check if your passengers are happy with the new course. You do not. You make the call that is right for the ship.
You say that is different.
Steve says it is exactly the same. Your developers might be perfectly happy building the way they have always built. Comfortable workflows. Established patterns. Known constraints. But comfortable is not the same as competitive. And you are not optimizing for developer comfort. You are optimizing for your organization's ability to compete and survive.
He is right. You know he is right.
Developer happiness matters. Of course it does. A happy crew is a good crew. But it is still a crew. And you are still the captain. Your job is to make the right strategic calls even when they are uncomfortable.
Bimini is visible on the horizon now. You need to start thinking about the approach.
You cannot lead transformation in something you do not understand operationally. Your team knows this. They can tell the difference between a leader who has done the work and one who has read about the work. And they definitely know when you are avoiding a hard decision by hiding behind their comfort level.
When you make architectural decisions about AI infrastructure adoption without operational experience, you are making them blind. You do not know what you are optimizing for. You cannot distinguish vendor marketing from operational reality. You cannot ask the right questions because you have not encountered the right problems.
Steve tells you to build something this weekend. He says he will help. He will even sign a non-disclosure agreement and be your intern. He tells you not to just get a demo or review the team's work. Actually write code using AI assistance and ship it to production.
You will learn more in that single iteration than you will in six months of reading analyst reports.
Steve drains his beer and grins. He says with the Series C money, they are hiring three more teams. He says if you ever want to actually work again instead of just reading about work, they compensate AI developers incredibly handsomely. He gestures at the boat around you and says since you own this wreck, you are probably better off staying where you are.
You tell him this wreck cost more than his first three funding rounds combined.
Steve says his burn rate is better. He is still grinning. He tells you to get in the boat. The nuclear submarine. Not this diesel-powered museum piece you are so proud of.
The submarine manual does not teach you how to operate a submarine. Operating the submarine teaches you how to operate the submarine.
You throttle down for the approach to Bimini. The conversation is over but the point landed.
Get in the boat.