Embrace The Ugly

One developer's unfiltered take on AI for business

I've been building software for almost 40 years. In the last 12 months, AI agents changed everything about how I work. This is what I've learned -- the good, the bad, and the ugly.

The Ugly Truth

People see what I produce and they're amazed. Then they see the screen I use to produce it and they run away.

Claude Code -- the AI tool I use every day -- looks like something from 1995. Black screen, white text, no buttons, no menus. It's a command line tool. It looks terrible. I stare at it sometimes 12 hours a day, and yes, it could be nicer.

But here's the thing: I've written more code in the last year than in the previous 29 years of my career. Some of what I've built in a weekend would normally take three to six months. We organized 20,000 to 30,000 product catalogs in a weekend. My son needed internship placements -- he spent all day and found 3. I sat down with Claude Code, it interviewed him for 10 minutes, then found 48 places and filled out the applications in another 10 minutes.

I haven't opened Word in six months. I rarely open Excel. I just ask Claude Code to handle it.

Don't equate ugly with broken. Don't equate ugly with half-done. Go look at how much money Anthropic is making off this tool. Some of us get it.

Remember Neo asleep at his desk, green text streaming down a black screen? Nobody watching that would say "that looks user-friendly." But that screen was the door to seeing everything. Follow the white rabbit. Take the red pill. The ugly terminal is the door.

If you look at the screen and want to run away -- run away. That's fine. This isn't for you. But if you care more about what it does than what it looks like, come on in.

In two or three months we'll probably have a prettier interface. But it doesn't matter. The ugly works right now.

And more often than not, I don't even look at the screen. I talk to it. I do 80% of my work with a microphone. We have voice interfaces, Teams integration. The screen sits in my office and the workers chug away. I check in. I give directions. I review the output. That's the job now.

The Objections Everyone Has

I've heard them all. Every single one. Here they are, and here's why most of them don't hold up.

"But it hallucinates"

Hire a new employee and tell me they never hallucinate. How often do you clean up after coworkers? How often do you have someone on the team who just doesn't care about the details? You accept human flaws every day. You can accept AI flaws too -- especially when you can actually fix them.

The best test I can give you: give the AI a task you already know how to do. Something you've been doing for 10 years. Compare the results. I bet you the agent does as good or better, if it's set up correctly.

You can also put guardrails around it. Tell it: if you claim something, prove it. Show me the link. Show me the source. Then you verify. You do that until you trust it in specific areas.

And here's the thing nobody wants to hear: when the AI gets it wrong, most of the time it's because you didn't tell it properly. We're terrible at giving clear instructions.

Here's a trick that fixes most problems: ramble at it. Say what you want in whatever messy way it comes out. Then ask: "Can you tell me what it is I'm asking you to do?" It says it back to you, structured and clear. You read it and realize that's not what you meant at all. So you correct it. You build the instructions together. This takes seconds.

"But what about privacy?"

First question I ask: where do you store your documents? Google Docs or OneDrive. Every time.

So you've already given all your data to Google or Microsoft. Every document, every spreadsheet, every email. But now you're worried about privacy? With AI?

If you trust Google, you trust OpenAI. If you trust Microsoft, you trust Anthropic. You're paying for the service. They say they're not using your data to train on. The privacy concern people have about AI specifically -- while their entire business lives on someone else's cloud -- doesn't hold up.

"AI writing is generic garbage"

If you're bad at using a hammer, you're going to hit your finger. Same thing here.

If you say "write me a proposal," you'll get generic output. You gave it nothing to work with.

The fix: don't start writing proposals. Start by setting up a writing style. Give it 20 of your old proposals. Tell it: write like this. It will write exactly like you -- spelling habits, sentence structure, everything. You do this once. Then every proposal, every email, every document comes out in your voice. Forever.

"Which AI tool should I pick?"

People spend weeks comparing Claude Code vs Cursor vs Copilot vs Codex vs Gemini and while they're comparing, they're using none of them.

That's like walking 100 kilometers because you can't decide between a Ford, a Volvo, and a Tesla. Pick one. Any of them is so much better than doing everything manually.

I pick Claude Code. I think it's currently the best for business output. Anthropic's output is polished, business-ready, professional. Google's looks like a PhD student made it. For business, that matters.

You can argue with me. I don't care. It's my choice. If you like it, come with me. If you don't, pick another one. Just don't walk.

What You Actually Need to Know

People make AI sound complicated. Agents, models, tokens, parameters. It's not complicated.

What AI actually is

A large language model is a super smart statistical machine that's really good at predicting what you'll say next. That's it.

It doesn't "know" math. Ask it something hard and it writes Python code to calculate it. Python is just a programming language -- and for the AI, programming languages are like any other language. It switches between English, French, and Python as easily as you switch between two languages you're fluent in.

When you take something that's really smart at talking and you give it tools -- the ability to write files, read spreadsheets, send emails -- now you have an agent. That's all an agent is. A smart talker with tools.

The three prerequisites

You need exactly three things:

1. The command line. That black screen with the blinking cursor. It's just talking to your computer with text instead of clicking. You need maybe 3-4 commands to get around. It's not hard.

2. File paths. Everything on your computer is in folders. Just like file cabinets in your office. A file path is just the address: which cabinet, which folder, which file. The backslash is just the separator. That's all it is.

3. Markdown. A text file with a few formatting characters. A hash sign makes a heading. Two stars make something bold. That's about it. When ChatGPT or Claude gives you a pretty response with headings and bold text -- that's markdown.

If you can handle those three things, I can show you how to run AI agents. The rest comes from there.

Skills and tools

A skill is a set of instructions telling the AI how to do something. Why is McDonald's so good? Amazing standard operating procedures. Same thing with AI.

A tool is the thing that does the actual work. It's the hammer. Claude Code doesn't know how to create an Excel spreadsheet on its own, so it writes Python on the fly. That works -- but if you give it a pre-built tool, it's faster.

Great tools with bad skills? That's a gorilla driving a Ferrari. You need both.

The Mentality Shift

Claude Code first, always

For almost a year, I've forced myself to go to Claude Code first for everything. I need to change the title of a Word document. I know how to open Word. It would take two minutes. I still go to Claude Code first.

In the beginning, your productivity will go down in some areas. Power through that. Because once you get past it, your productivity doesn't just double. I'm doing the job of a team of 10.

I'm a long-time freediver. My coach once said: don't jump in the ocean with a monofin and go spearfishing, because a shark will think you're an injured dolphin. A monofin swimmer is fast compared to a human. Compared to a dolphin? Still slow. People who don't use these tools are the monofin swimmers.

Context switching is the new core skill

As a manager, you switch context maybe several times a day when employees come to you. Working with AI agents? You do that 200 times a day.

When I started, I could manage two agents at once. Now I run six to ten regularly. It's a muscle you build. I have maybe four to six good hours of heavy parallel work, then it drops off. At some point you just run out of good.

My garage has never been cleaner. When you're running six agents and waiting for responses, you do five-minute cleanups all day.

Your identity changes

I've been programming since the late 1980s. Within a year of using AI agents, I no longer do what I trained to do my entire life.

My skill went from being a creator and writer of code to being a manager of six to ten occasionally drunk PhD students. There were genuine moments where I wondered: can I even call myself a developer anymore?

I played basketball my whole life at a high level. Knee injury ended it. Missed it for a long time. Started freediving instead -- completely different, meditative, quiet. Now I don't miss basketball at all. Things change. You become something different.

I haven't written a single line of code in probably six months. I don't miss it. I'm still a creator. I'm just a faster creator who doesn't go as low.

The Honest Parts

The cost is almost embarrassing

My tools are free. Claude Max is $100 a month. That's it.

We recently translated 350 website pages into seven languages. Cost: just under $18. Three years ago? $2,000 to $5,000 per language, two weeks of waiting. We did it overnight.

Even if you're faster at a single task, the AI can do 10 of them at the same time. You can't.

When it breaks

Claude Code has never deleted something on my computer that was not my fault. What it does do is waste my time by going in circles.

The other day we spent four and a half hours trying to fix something. Finally I said: start over from scratch. It picked a different approach and everything worked. When I asked why, it said the two tools it was using didn't work together.

That happens every week. I do three months of work in a week, then lose half a day. The ratio is still overwhelmingly positive. It's like a waiter that sells ten times more than anyone else but spills on the carpet once in a while.

Running with permissions off

I run Claude Code with all permissions turned off. It doesn't ask before every file change. Anthropic is a security-focused company, and the agents know what's safe.

Start small. Give it access to one folder. Back it up first. When you're comfortable, expand. Eventually you end up like me -- it has access to OneDrive, email, calendar.

But I still read every single email that goes out. Every message posted anywhere. I'm not ready for full autonomy on communications. Most of what you do is a two-way door -- if a spreadsheet gets messed up, you're losing 5 minutes, not 30 hours.

But I'm Not Technical

I get this one a lot. "You're a developer. Of course this works for you."

Partly true. But I'm also a product creator. Product creators take complicated problems and make them simple. That's what a lemon squeezer does -- somebody took the problem of juicing a lemon and made it effortless.

Claude Code is an incredible engine. I'm the chassis. I don't make the engine faster. I wrap it in something that makes it drivable for people who aren't mechanics.

And here's the honest part: you don't need me. Once you install Claude Code, you can figure it all out yourself. We just shortcut it. Like a personal trainer -- you don't need one for the gym. You get one to get motivated and get there faster.

The difference between a developer and a non-developer isn't intelligence. It's who you call when you get stuck. Developers have nobody to call. Normal people do. They can call developers.

Getting Started

You want to start tonight? Here's what you do.

Download the Director from my website. It walks you through installing Claude Code and all the tools. Click, click, answer questions, done. You're up and running with more tools than any other platform, pre-installed, for free.

If you don't like my opinions, install Claude Code directly from Anthropic. Same engine, just without the chassis.

Then: pick a folder of your work. Back it up. Start asking questions -- what's in these spreadsheets, what's the average in column three, why are these files here.

Then feed it your old work. Got 20 proposals? Tell it to extract your writing style. Read what it says about how you write. Then give it a real new request and tell it to write in your voice. Watch it produce a finished document in two minutes that would have taken you an hour.

That's when the light bulb goes on.

The Close

If you're building a deck and you've got 50 boards to cut, there are two kinds of people.

The one who measures every single board.

And the one who builds a jig for the saw. Cuts the first board, measures it, gets it right. Then the next 49 boards are just: put it in the jig and cut. No measuring.

I'm the second person. I will do a lot of work to not do work.

If you're someone who likes to set up systems, organize things, and streamline processes so you do less monotonous work -- join the AI revolution.

If you're stuck in the old ways and can't get past how the screen looks -- don't join us.

But whatever you do: embrace the ugly.

Want the Shortcut?

Everything above is free. Learn it yourself, at your own pace. If you want me to set it all up on your laptop and teach you in person, I run a two-day course in Toronto.

Subscribe on YouTube: @cc-EmbraceTheUgly