top of page

I Got the Dress Code Wrong

2 hours ago
7 min read
A fuzzy white plush bear mascot with glowing red eyes and a smirk stands raising one arm in a dark room lit by red and blue light, with abstract data patterns and smoke behind it

In February 2026, I wrote an article about the emerging value of the fluent AI operator. You know the type. Hoodie-wearing nerd in the corner, headphones on, weird relationship with time, drinking entirely too much coffee.


Although, for the record, there's no such thing as too much coffee. Let's not get ridiculous.


Anyway, the person who's quietly building things, experimenting with AI, and accomplishing things that would have required an entire team a couple of years ago. I argued that these people were becoming extraordinarily valuable and that companies had better start finding them.


Well, I had a conversation with a client that made me realize something.

I got the dress code wrong. Apparently, I just assumed everyone dressed like me. LOL.


She's a corporate trainer at a large company. We've been working together for nearly two years, and she's been experimenting with AI, developing training applications, building workflows, and generally geeking out on this stuff every chance she gets. And here's what's interesting. Of the hundreds of people I've worked with on AI, she's probably the first one I've watched come this close to making the entire transition.


Not just learning the tools. Becoming the operator. And the funny part is, I don't think she fully realizes it yet.


You're Worried About the Wrong Job

She was telling me about a training application she'd just built using Copilot. Branching scenarios, assessments, HTML, and eventually integration with a corporate learning management system. The sort of thing that traditionally involves a developer, an instructional designer, six meetings, and somebody from IT explaining why you can't do it.


She'd basically built the damn thing herself. Still needed testing, sure. But she had a working prototype. And then she said something that cracked me up.


"I'm not gonna have a job for much longer if people figure this shit out."


Dude.


You've got this completely backward.


I told her that the people around her should probably be a hell of a lot more worried about losing her. Because when the rest of her organization finally figures out what this technology is capable of, they're going to be looking for somebody who can help them navigate it. And she's already there.


But here's the important part.


She doesn't necessarily know how to do any of the things she's going to be asked to do next.

Neither do I, half the time. That's the whole point. The fluency isn't knowing the answers. It's knowing how to find them. It's creativity, curiosity, systems thinking, and an intuitive understanding of the capabilities sitting in front of you. And that takes reps. Call it kung fu. Call it the Force. Whatever. You don't develop it by watching somebody else swing the lightsaber. You develop it by doing.


It's becoming comfortable walking into a problem you've never encountered before and saying, "I have absolutely no idea how to do that. Let's find out."


That's the operator.


Not somebody who memorized a thousand prompts or knows which buttons to push. Somebody who's comfortable in an environment where not knowing how to do something is no longer much of an obstacle to getting started.

That's a fundamentally different relationship with technology. And eventually, a fundamentally different relationship with time.


The GitHub Conversation

Toward the end of our conversation, she mentioned another problem involving employee recertification and tracking.


I asked if she'd looked on GitHub.


She hadn't.


Now, I've been preaching about GitHub for years, but AI has turned that place into an absolute candy store.


Millions upon millions of software repositories. Applications, tools, libraries, frameworks. An enormous collection of things people have already figured out how to build. And a tremendous amount of it is open source. Historically, the catch was that you needed to know how to program to do much with it.


Well, not so much anymore.


Now you can find a repository, hand it to an AI coding agent, and say, "Hey, what does this thing do? Can we make it do this other thing?"

And the agent can help you figure it out. Understand the code. Modify it. Connect it to something else. Build an interface. Test it. Obviously, security, licensing, and whether the software actually works still matter. We're not throwing random GitHub code onto corporate servers and hoping for the best. But think about what just happened.


An enormous library of software capabilities that previously required specialized technical knowledge to access is becoming available to people who understand problems but don't necessarily know how to program solutions. That's ridiculous.


It's like somebody handed you the keys to a gigantic warehouse full of LEGO bricks and a robot that knows how to assemble them. You just have to figure out what you want to build. So I told her to search GitHub for open-source recertification projects. She started looking while we were still on the phone. A few moments later, she was finding things worth exploring.

And she was excited about it.


That's the part I want you to notice.


The Curiosity Is the Engine

She wasn't excited because she'd just been assigned another task. She was excited because she'd discovered another possibility. Another rabbit hole. Another collection of things she didn't know existed five minutes earlier.

And now she wanted to see what she could do with them.


That's the pattern.


Curiosity leads to experimentation. Experimentation reveals a capability. Eventually, you build something that actually works.


And there's your dopamine hit... Holy shit. I just did that.

Now you want to do it again. Except this time you've got another tool, another capability, another little piece of understanding you didn't have before. And the cycle repeats. That's how you become fluent.


Not by sitting through another presentation about the future of AI.

By getting your hands dirty and discovering what happens when you start connecting things.


She's spent a tremendous amount of time doing exactly that on her own. No grand training program. No appointed AI guru. No Mr. Miyagi standing behind her telling her to wax on, wax off. Just genuine curiosity, a willingness to experiment, and enough excitement about the technology to keep going when things got frustrating.


And after enough repetitions, something changes.


You stop thinking about AI as an application you occasionally open.

It becomes the environment you work inside. Think about the software suites we've used for decades. Microsoft Office, Adobe, all those ecosystems we learned to navigate. Over time, the environment itself became valuable because we knew how to work within it. Now imagine an environment where the tools aren't just sitting there waiting for you to learn them.


You can ask the environment to help you understand, create, connect, or even build the tool you need. That's a pretty significant change. The way you approach problems changes. The way you use information changes. Your expectations about what you can accomplish in an afternoon change. Eventually, you're not really working the same way as everyone around you anymore. And that's where she's getting to.


Find One. Or Become One.

I've had variations of this conversation with Uber drivers, CEOs, entrepreneurs, accountants, and just about everyone in between. The advice is almost always the same.


Stop waiting.


Stop waiting for your employer to develop an AI strategy. Stop waiting for somebody to tell you which certification to get or which application to learn. Pick something that interests you. Something you understand. Something that's been annoying you for years. Something you've always wanted to build. Then go see what's possible. Ask AI questions. Explore GitHub. Try things. Break stuff. Figure out why it broke. Ask AI to help you fix it. And don't get discouraged when something blows up in your face.


The burn is as useful as the build.


Sometimes more useful. That's where you discover the limitations, learn what actually works, and develop the instincts you can't get from watching a tutorial. You don't need to know what you're doing. You need to become comfortable figuring it out. And if you're running a company, you really need to start looking for these people. Because the person who can help transform your organization might already be working there.


They might be in accounting, marketing, operations, or, as it turns out, corporate training. They might not have a technical background at all.

But they've developed something increasingly valuable: the confidence, creativity, and curiosity to explore capabilities that most people don't even realize exist yet.


Find them. Encourage them. Give them room to experiment. And if you can't find one? Become one.


Maybe I've Been Building the Wrong Thing

This conversation clarified something I'd been circling for a while.


I've spent years building AI applications, tools, automations, and all sorts of ridiculous experiments. And I love that stuff. But I'm increasingly convinced that the most important thing I can build now isn't another application.


It's capable AI operators.


People who understand the possibilities well enough to find their own solutions. People who are creative, curious, adaptable, and completely unafraid of technology they haven't encountered yet. Because the models will change. The tools will change. The interfaces will change. But that ability to look at something unfamiliar and confidently say, "Let's figure this shit out"? That's going to be worth a fortune.


And I'm watching it happen right in front of me.


When we started working together, she was curious about AI. Now I'm watching her become exactly the kind of operator I've been telling companies they need to find.


She's not there because she knows everything. She's there because she's no longer intimidated by what she doesn't know. And that's a capability anyone willing to put in the work can start developing.


The next few years are going to be interesting. Because eventually the rest of the world is going to catch up, and a whole lot of people are going to discover that the rules of the game have changed.


Meanwhile, those who've spent this time experimenting will already be comfortable in the new environment. They'll know where to find the magic wands. They'll know how to figure out the spells. And they'll be the ones everyone else comes looking for.


You can wait around hoping to find one of those people.

Or you can become one.

Personally, I'd recommend the second option.

---


Rich Washburn is a technologist, strategist, and Founder & Chief AI Architect of ARIA AI Labs, working at the intersection of AI, infrastructure, communications, and capital. He also serves as Managing Partner and Chief AI Officer at Eliakim Capital.

Comments


Animated coffee.gif
cup2 trans.fw.png

© 2018 Rich Washburn

bottom of page