RightTech, 9450 SW Gemini, Beaverton, OR (2026)

05/24/2026

I’ve tried a lot of task trackers over the years.

Monday.
Asana.
A few others I’ve probably forgotten.

They were polished.

They were feature-rich.

They just never fit the way I actually work.

My days are pretty disjointed.

I context shift a lot.

That’s not a bug for me... it’s how I operate.

The problem was every tool seemed built for someone with a neat, linear day.

So I built a small one for myself.

Nothing huge.

Just a simple custom task tracker with a little AI agent, which is just software that can make suggestions based on rules and context.

I can drop in a task and say:

It’ll take an hour.

It’s high impact.

It’s urgent.

Then it looks at my calendar for the week, uses the prioritisation rules I’ve trained it on, and suggests where the task should actually go.

As new tasks come in, I can quite literally just tell it, and it reshuffles things around what already exists.

That ended up being more useful than all the polished software I’d tried before.

Not because it had more features.

Because it matched how I make decisions.

That’s the shift I think a lot of people are starting to see now.

Literally anyone can now build software.

The bottleneck is no longer skill.

It really is imagination at this point.

A tool does not need to be massive to be powerful.

It just needs to fit the real work.

What’s one tool you wish worked more like your brain does?

05/23/2026

The fastest way to turn a cheap AI experiment into an expensive mess...

is to forget two boring things:

usage limits

and security basics.

AI makes building feel easy now.

Literally anyone can now build software.

That’s the good news.

The bad news is it’s also very easy to make mistakes and expose things that shouldn’t be exposed when working with AI.

I’ve seen people spin up a little app in an afternoon, connect it to an AI model, test it a few times... then realise they left the door wide open.

No spend cap.

No access rules.

API keys sitting in the code.

An API key is basically a password that lets software talk to another tool.

If that gets exposed, someone else can use your account and your balance.

Now your “tiny test” is buying tokens all night while you sleep.

And yes... the bill can get stupid fast.

The bottleneck is no longer skill. It really is imagination at this point.

Claude Code and Codeex can basically do anything you can imagine with them.

But imagination without guard rails is how you accidentally fund a robot’s weekend.

So before launch, I check 3 things:

Set a spend cap

Hide keys properly

Decide who can access what

We’re actually entering an age where it’s getting even easier for people.

That makes the basics matter more, not less.

Build with tech, not teams...

but don’t build yourself a surprise invoice.

What’s the worst AI mistake you’ve seen so far?

05/22/2026

Live AI builds look a lot more magical from the outside than they feel in the room.

What actually happens is pretty ordinary.

I pick a folder on my computer.

That just means the place where the app files will live.

Then I open the coding tool and switch on plan mode.

Plan mode is exactly what it sounds like.

Before it writes code, it thinks through the steps.

That part matters more than people realise...

I really want people to see how easy this is now.

Hopefully by the end of a session, you can see that literally anyone can now build software.

We’re entering an age where it’s getting even easier for people, and the bottleneck is no longer skill.

It really is imagination at this point.

From there, I give it a plain English prompt.

What the app should do.

What screen I need first.

What data it needs to store.

Then the tool starts building.

Claude Code and Codeex can basically do anything you can imagine with them, but the process still helps when you keep it simple.

Setup.

Planning.

Implementation.

Quick testing in the browser.

That last bit is my favourite.

You open the first version, click around, spot what’s off, and tighten it up straight away.

Nothing mystical.

No big team.

Build with tech, not teams.

You’ll see today exactly how easy it is with Codeex once you break it into small steps.

If you’ve never watched a live build before, that’s the real surprise... it’s calmer than you think.

What part of the process feels confusing from the outside?

05/21/2026

If an AI tool can build the app for me... what exactly am I still meant to do?

Quite a lot, actually.

Literally anyone can now build software.

We’re entering an age where it’s getting even easier for people.

Claude Code and Codex can basically do anything you can imagine with them.

But that does not mean you hand over your brain and hope for the best.

The bottleneck is no longer skill.

It really is imagination... and judgment.

What I still do myself is pretty simple.

I define the goal.

I explain the workflow in plain English.

I test whether the thing works in the real world.

And I look for risks.

That last part matters more than people think.

It is very easy to make mistakes and expose things that should not be exposed when working with AI.

So before I trust a build, I check things like:

Who can access this?

What data is it storing?

What happens if a user clicks the wrong thing?

Does this actually solve the problem I asked it to solve?

We’ve used AI to create our own internal tools and social media systems.

This is all vibe coded.

We put our money where our mouth is.

But even then, we do not blindly trust the output.

AI is fast.

It is not accountable.

Your job is to be the one with context, standards, and common sense.

That is the work.

How much of your build process do you still keep in human hands?

05/20/2026

The small build habit that saves me hours is boring...

I fix one thing at a time.

When I’m working with AI on a bug fix, the worst move is throwing five problems into one prompt and hoping for a clean result.

That’s how a quick repair turns into a full afternoon of chaos.

AI coding tools like Claude Code and Codeex are good enough now that literally anyone can now build software.

We’re entering an age where it’s getting even easier for people.

But easier to build does not mean easier to debug if you get sloppy.

Here’s the simple way I handle it:

1. Pick the single problem that hurts most.
If the login is broken, start there.
Not login, layout, emails, and reporting all at once.

2. Describe what is happening in plain English.
What did you expect?
What actually happened?
What error showed up?
That gives the AI something clear to work with.

3. Ask for one fix.
Not a redesign.
Not “clean up the whole app.”
Just one issue.

4. Test that change before moving on.
If it works, great.
Then do the next problem.

This habit matters because the bottleneck is no longer skill.

It really is imagination... and discipline.

You can basically do anything you can imagine with these tools.

But if you stack too many requests together, you make it harder to see what actually fixed the problem... or what broke something new.

Simple builds stay simple when your fixes stay small.

How do you handle debugging with AI right now?

05/19/2026

A weird thing happens when people start building with AI...

They ask for a simple app.

The coding tool suggests React.

Then they assume React must be the right answer.

It often isn’t.

React is a popular way to build web apps. It’s powerful.

It’s also something AI models suggest a lot because they’ve seen so much of it.

That’s training bias.

The model isn’t always choosing the best tool for your job.

It’s often choosing the tool it has seen the most.

That matters because literally anyone can now build software.

We’re entering an age where it’s getting even easier for people.

So the goal is not to use the fanciest stack.

It’s to build with tech not teams.

If a plain HTML page, a bit of JavaScript, and a simple backend will do the job... use that.

If Cloudflare can host it on a generous free plan... even better.

You don’t necessarily need the overhead of these other tools.

Same rule we’ve used in our own builds.

We’ve replaced software from a stack that grew past $2,000 a month.

Not by rebuilding giant SaaS products.

By taking the pieces we actually needed.

That’s the shift.

Software shouldn’t be the limiting factor to growing your business.

The bottleneck is no longer skill.

It’s imagination... and choosing simple when simple works.

Have you had AI suggest a stack that felt wildly overbuilt for what you needed?

05/18/2026

We put our money where our mouth is.

Damien and I went through our own tech stack and asked a simple question...

What are we actually using?

At the time, we were paying about $2,000 a month in software licenses.

Probably more now if we had kept them all.

This is not an attack on SaaS tools.

A SaaS tool is just software you pay to use each month.

A lot of them are excellent.

The problem was simpler than that.

We were often paying $97 a month... $197 a month... sometimes more...

And only using 10% of what the tool could do.

So we started replacing small parts of those tools with smaller internal apps built with AI.

Not giant rebuilds.

Not trying to outdo companies that had spent millions building polished platforms.

Just taking the one workflow we actually needed...

And building that.

That shift taught me something useful.

Expensive software is not always expensive because your business is complex.

Sometimes it is expensive because you bought a whole department store when you only needed one shelf.

That is why I keep saying software and the cost of software should not be the limiting factor to growing your business.

We replaced tools for content, scheduling, and outreach.

In many cases, the running cost dropped to cents.

A post might cost 15 cents.

An image around 3 cents.

A video maybe a dollar.

Literally anyone can now build software.

The bottleneck is no longer skill.

It really is imagination.

Have you looked at your software stack lately and asked what you actually use?

05/17/2026

The shift hit me all at once...

Software stopped feeling like something reserved for technical people.

It started feeling like something I could actually build.

For years, I treated software like a specialist sport.

You needed a dev team.

A budget.

Time.

A lot of patience.

Now... literally anyone can build software.

That sounds like hype until you try it.

What changed for me was seeing tools like Claude Code and Codex take a plain English idea and turn it into something real.

Not perfect.

Not some giant SaaS platform built by a team of 50.

But real enough to test.

Real enough to use.

Real enough to help a business grow.

That was the mental shift.

Software and the cost of software should not be the limiting factor anymore.

We’re entering an age where it’s getting easier fast.

The bottleneck is no longer skill.

It’s imagination.

And the willingness to test a small idea instead of just talking about it.

That’s why Damian and I got so excited about this.

So many people had a barrier to entry before.

Now that barrier is much lower.

You can build with tech, not teams.

You can start with one messy problem.

One workflow.

One annoying task.

Then see if AI can help you turn it into a simple app.

That’s the moment things changed for me.

Not when I became technical.

When I realised I didn’t need to be.

What small thing would you build if you stopped assuming software was out of reach?

05/16/2026

A lot of software pricing works like this...

You walk in needing a screwdriver.

They sell you a space station.

That is the bit that finally started annoying me.

Not because the tools are bad.

This is not an attack on SaaS tools... software you pay for monthly online.

A lot of them are excellent.

The problem is simpler than that.

You might be paying $97 a month. Or $197 a month.

And getting a very fully featured product.

But in real life, you are often using 10% of it.

Maybe one report.

One automation.

One awkward little feature buried in tab 7 that your whole process now depends on.

We went through our own stack and found we were spending about $2,000 a month on software licenses.

Not because we needed thousands of dollars of capability.

Because we needed small pieces of a lot of different tools.

That changed how I think about software.

The question stopped being, "What platform do we need?"

It became, "What do we actually use?"

That shift matters because literally anyone can now build software.

We are entering an age where it is getting even easier.

The bottleneck is no longer skill.

It is imagination.

Tools like Claude Code and Codex mean you can build with tech not teams... and you do not necessarily need the overhead of all these giant platforms.

Not to rebuild everything.

Just to create the part you actually need.

That is usually the expensive bit anyway.

Have you got a tool you pay for mainly to use one tiny corner of it?

05/15/2026

The quality of an AI build is usually decided before the build starts.

Not in the code.

In the brief.

I’ve learned that if I spend 10 minutes turning a messy idea into a simple MVP brief, I get a better first version and far fewer fixes later.

MVP just means the simplest usable version.

This matters now because literally anyone can build software.

We’re entering an age where it’s getting even easier for people.

The bottleneck is no longer skill.

It really is imagination at this point.

Here’s the process I use before I let Claude Code or Codex touch anything.

1. Start with the brain dump

I write the idea exactly as it comes out of my head.

Usually messy.

Something like... “I want a habit tracker that reminds people, shows streaks, and feels simple.”

2. Force the use case

I ask, who is this for and what do they need to do first?

Not every possible feature.

Just the core job.

3. Ask follow-up questions

What should happen when they log in?

What should they see first?

What needs to be saved?

What can wait?

This is the part that saves me.

4. Turn it into a build brief

I write a short spec with the pages, actions, and basic rules.

Nothing fancy.

Just enough that the AI has clear instructions.

5. Then build

I really want people to see how easy this is now.

You don’t necessarily need the overhead of other tools.

If the brief is clear, AI can do a lot.

If it’s vague, you’ll get chaos dressed up as progress.

Do you brief your ideas first... or prompt on the fly?

RightTech

05/24/2026

05/23/2026

05/22/2026

05/21/2026

05/20/2026

05/19/2026

05/18/2026

05/17/2026

05/16/2026

05/15/2026

Address

Website

Alerts

Shortcuts

Share

Category