Brian Witten

If you're not using Cloud Code in 2026, you're going to fall behind.

I'm switching from Cursor to Cloud Code today based on all the hype.

This is wild.

This is actually wild.

Sometimes I like to call it journalism at scale.

I'll build a lot of tools for reporters, investigative tools, reporting tools, things to help them analyze stuff that we can put together.

And sometimes I'll build interactive things for readers to click on, which is nice because then I can show my parents something and be like, I built that and they'll understand what I do.

I guess, first, I was just, like, super impressed and glad to see more people messing around with this kind of stuff because...

These coding agents kind of turn everybody into a developer, which is exciting for me because that means you can be doing more things and all of the responsibility doesn't necessarily fall down to one person when it comes to building tools or building things.

But as Brian dug into the code, he saw that not everything was perfect.

At first, I saw a lot of outdated practices in the code, looking like it had been coded in the late 90s.

There were significant problems with accessibility.

You couldn't really use the keyboard to do things.

If you were using a screen reader, you'd have no idea what was going on.

The styles needed updating.

It would have clashed with stuff on the page.

It did stuff that would have kind of made the rest of the page look like a mess if we'd left it in there.

Oh, and there was a bug.

As someone who uses cloud code all day, every day, I feel safe because maybe I'm being short-sighted, but it seems like the more I use these things and the more I build with them, there's a limit to how satisfying the result is without a person noticing.

seriously directing it and adjusting what it's producing.