Hey, I'm Cam. I build systems, businesses, and weird ideas.

I look at things in about this order.

What is happening?

I notice the pieces first. What connects, what doesn't, and where a person is being asked to hold the whole thing together.

How I Think

I don't build because building is the point. I build because I paid attention long enough to know what needed to exist.

You can't automate a mess

If a process is broken and you automate it, you don't get a fixed process. You get a broken one running faster, with less time to notice.

So the first question isn't what to build. It's whether there's anything there to build on.

A messy process still has a shape. You can describe it, even if describing it is embarrassing. Somebody can walk you through how a job gets from a phone call to an invoice, and it's ugly, and it works. That's fixable.

A broken process doesn't know what shape it's supposed to be. Ask where it ends up and nobody can tell you. Not because they're hiding it. Because it genuinely doesn't have an ending yet.

The test I use is whether someone can describe the conveyor belt. Where does the work enter, what happens to it, where does it come out. If we work at it together and still can't get there, that's the answer. Identify it, then either fix that first or walk away.

Walking away is the part I'm still not good at.

Why before how

I used to start with how can I build this. That question is fun and it will happily eat a month.

Now I try to start with why does this need to exist.

It's a worse question in the sense that it's less enjoyable. It's a better question in the sense that it occasionally stops me.

This is the oldest thing about how I think, and I only recently started applying it to my own work.

Restraint for meaning

Complexity is the ruin of simplicity. And simplicity can cause complexity.

The second half is the part people skip. Strip a system down too far and you don't get elegance, you get a gap, and someone fills that gap manually, forever, and calls it their job. Oversimplifying is just relocating the complexity onto a person.

So restraint isn't minimalism. It's deciding what a thing is for and refusing to make it do anything else.

The clearest version I've actually managed: I didn't build the AI workforce product. The idea was interesting and I could have built it. But the timing was wrong and so was the ownership model, and neither of those gets fixed by building the thing well. A good idea at the wrong stage is still the wrong thing to build.

I'm careful about claiming this one. Building is my comfort zone. When I'm stuck, the honest description of what I do is build more: more research, more organizing, another tool, another system. Restraint is the principle I hold most confidently and practice least consistently.

I'd rather say that plainly than pretend the discipline is settled.

Systems should serve people

The purpose of a system is to give somebody back time, clarity, and capability. If it doesn't do one of those three, it's overhead wearing a nicer interface.

Most systems fail the same way. They leave a gap, and a person becomes the connective tissue between the parts that don't talk. That person gets good at it. Then they can't take a week off, and everyone calls that being indispensable.

Nobody should have to be the glue.

Show the thinking, not just the output

A finished thing tells you almost nothing. It doesn't tell you what got rejected, what the tradeoff was, or where it's fragile.

So I try to show reasoning, including the parts that didn't work. That includes saying what I don't know as plainly as what I do.

The version I actually practice: auditing what's already running instead of building the next thing. Checking that a status which says a task completed matches what actually happened, not just that the script didn't crash. It's less exciting than shipping something new. It's also the difference between a system I trust and one that looks like it's working.

I've been on the wrong end of that.

The uncomfortable part is that showing your reasoning also shows your gaps, and I don't always want to.

Trust over hype

The pattern I keep watching: something gets funded, gets loud, promises autonomy it can't deliver, and the people paying for it find out later. The market is paying for the pitch, not the execution.

I'm not interested in being on that side of it. No percentages I can't back. No promises made to close something. Being straight about where the tooling actually is rather than where the demo suggests it might be.

The tension I live with is that conviction is easy to confuse with evidence. I believe this approach is right. I don't have proof yet. Those are different things and I try not to blur them.

System lines become topographic lines. Connection becomes roots. Interface becomes human.

Cam wearing glasses and a beanie, wrapped in a pizza-print blanket.

Why is it this way?

It walked. I needed to know why.

I was around eight when I took the robot apart.

It walked. That seemed like the whole point of it. I wanted to know why it walked, so I opened it up and looked.

That's the part that stuck. Not the robot. The question.

Tron was the first movie that made me look at the world differently. I was already the kid taking things apart, and here was a movie telling me the inside was worth seeing.

Birthdays at Nickelcade. Neon light, arcade noise. Journey, Depeche Mode, Chicago underneath all of it.

Comics came from my grandma. Batman Beyond is still my favorite.

The 80s built things to last. No planned obsolescence, no shortcuts. I didn't have words for that then. I just knew those machines felt built on purpose.

Eleven years

I started in sales, eleven years of it, beginning with customer-facing work at sixteen. What I kept learning wasn't really about selling. It was about paying attention: why people decide the way they do, where trust breaks down, and where the systems around them create friction.

Sales taught me it's fine to fall on your face. No's don't mean no. They get you to the next yes. The bigger lesson took longer, and I still repeat it to myself: some days you gotta sit in the shit. Growth doesn't come from comfort.

The tools were fine. Every one of them was capable and well built and did what it said on the box. What wasn't connected was everything between them. Every new deal started back at the drawing board. Somebody rebuilding context that already existed somewhere else. Pulling information out of one system by hand to get it into another. Reconnecting pieces that had been connected last week, by a different person, for a different deal.

The software wasn't the problem. The space between the software was the problem. And there was always a person standing in that space, holding both ends.

I kept bringing it up. I'd show up prepared. Build a demonstration nobody asked for. Put together a small tool to show what I meant. Try to explain why a different approach would hold up better.

Mostly it didn't land. The preparation didn't register. The approach was different enough that it read as a detour.

For years I thought the way I think was the problem.

The glue

In 2025 I was the back office for two financial advisers. Both of them. One person.

None of it was hard on its own. What was hard was that I was the only place all of it connected. The business ran because I remembered how the pieces fit together.

Then I sent a financial plan to the wrong client.

Moving too fast, not paying attention, didn't check the recipient before it went out. That one's mine. But I had also become the only safeguard in a process that needed more than one, and nobody had noticed that, including me.

I could see the shape of the fix. I couldn't build it. Financial services is regulated for good reasons and the constraints were real. You don't casually redesign a workflow with compliance sitting on top of it. So I understood the problem and had no way to touch it.

I was still inside the system.

The advisers who grew got out from under their own operation. The ones who stalled got buried in it. That had nothing to do with how good they were at the actual job.

Not better. Supported.

What changed it was talking to people doing my job on bigger teams.

They weren't better at it than I was. They had somebody who handled paperwork and only paperwork. Somebody whose entire job was scheduling. A person to hand a thing to when it left their lane. Nobody was carrying the whole shape of it in their head, because nobody had to.

The difference wasn't the people. It was that the work had somewhere to go.

So the question changed. Not why is this so heavy. That one I already knew the answer to. The new one was whether technology could do some of what a bigger team does. Not replace anybody. Just hold the parts that shouldn't have to live in one person's memory.

Building it anyway

Around December 2025 I was working part time, in the middle of a transition, trying to build a path toward work that actually fit.

What I wanted was specific. Operations. Enablement. Training. Systems. Technology pointed at how people actually work instead of at how a demo works.

I wasn't trying to escape anything. This was never an exit. It was about fit.

Money was part of it. I'm not going to pretend it wasn't. It just wasn't the reason.

The reason was ownership, and I don't mean control. I wanted to be responsible for something. Something that would keep working when I wasn't in the room, and that could reach more people than I can one at a time.

So I started building. Not because anything had happened to me. Because that was already the direction I was headed.

Overlooked again

Then in April 2026 I applied for an internal role and didn't get it.

The role wasn't about AI. It was about helping people get back into the workforce, people who'd been out a while and were trying to come back. Teaching. Sitting with somebody while their confidence rebuilt. Taking something complicated and making it usable for a person who needs it to be usable.

I was more upset than I expected to be. Butt hurt, honestly. A little sad, because I really did like the job and I liked what that job would have been.

And it landed on something older. Overlooked again, not by anyone in particular. Just the same pattern I'd been walking into for years. Prepared, and it doesn't register. A different approach, and it reads as the wrong one.

The thing I spent years trying to fix became the thing I learned to use.

I don't think of myself as an AI person. AI is the current tool for a question I've been asking since I was eight. What I actually care about is the space between technology and people. Building the thing around how a person really works, and helping somebody trust it enough to use it. A system nobody understands or trusts isn't a system. It's just more work.

Nobody should have to be the glue.

I was the glue, for two people, for a while, and the business worked because I was there holding it. That isn't a compliment to me. It's a design flaw.

What I'm Building

None of these started as something I wanted to build. They started as something I noticed and couldn't leave alone.

Neon Ridge Systems

This site is about why. Neon Ridge Systems is where it has to survive contact with a real operation, a real budget, and a real person who has to use it on a Tuesday.

I run it on the same infrastructure I'd build for anyone else. I needed to know whether the approach held up before I asked somebody to pay for it. It does, for me. No client has run one of these systems yet.

The Grid

Humans should not be the integration layer. That's the sentence the whole thing came from.

I spent years being the connective tissue between tools that each worked perfectly on their own. Carrying context from one system to another because nothing else would. The tools weren't the problem. The space between them was, and a person was always standing in it.

At some point that stopped being a complaint and became a question I could build against. The question came first. The software came second. That order matters to me more than the software does.

It's a personal operating environment I built for myself. It isn't a product, and I'm not going to describe it as one.

Signal

Signal is why this site exists rather than a résumé.

The world is not short of tools, trends, frameworks, or predictions. It produces those constantly and they arrive already certain. What's short is reasoning you can inspect.

So Signal looks at what's actually happening, why it matters, and what pattern sits underneath. Not another answer to follow. The thinking, shown, so you can decide whether you agree with it.

It's starting. No publishing schedule, and I'm not going to promise one.

The one I didn't build

An AI workforce product. A good idea at the wrong stage is still the wrong thing to build.

Unseen Paws

Some of this has nothing to do with business.

I've been helping build the website and proof of concept for Unseen Paws while it gets off the ground. My part is the infrastructure and systems. Not the strategy, not the programs, not the mission. The plumbing underneath it.

Small organizations run into exactly the problem I keep writing about, with less room to absorb it. One person can end up holding everything. That's the part I can actually help with.

It's early. There is a real beginning now, not a finished story.

Now

Updated

Here's what's currently open in my head.

Some of it is becoming a thing. Some of it is just refusing to leave.

Building right now

Making this site feel like me, not like a very competent website about me.

That distinction has taken longer than I expected.

Thinking about

What changes when one person can coordinate an entire AI operating environment?

Not fake autonomy. Not a pile of tools reporting success. Something inspectable that actually helps a person carry less.

Current obsession

Mammoth hockey.

I have been counting down long enough that current obsession is probably the honest label.

Still in the pile

Batman Beyond, exploded devices, and comic panels that know exactly when to break the frame.

Apparently this is also how I build a website now.

Still hard

Trusting myself.

Continuing to believe there's something worth having in how I think, on the days the evidence is thin.

Building versus selling. Building is the natural part. Putting the thing in front of people is the part I avoid, and I know that I avoid it. Knowing has not magically made it easy.

Still open

How do I turn the way I naturally think into something useful for other people?

And how do I do that without sanding off the weird parts that make it mine?

How do I stop surviving and start building the life I actually want?

Follow the Signal

Most advice skips the part I care about: why. Signal is where I work that part out in public.

The status said done. The work wasn't.

I spent a week not building anything new and went looking at what was already running instead. Not because something broke. Because nothing had, which is its own kind of suspicious.

One of the statuses was lying. It had advanced a record past a stage where it should have stopped, reported success, and carried on. The log was clean. The outcome was wrong.

It didn't fail. It reported.

Tools are good at telling you they ran. They're much worse at telling you whether the work happened. And the further a tool sits from the actual outcome, the wider that gap gets. Which is inconvenient, because coordination is what nearly everything is being sold as now.

A tool that does one job badly, you notice in an afternoon. A tool that claims to connect five things and connects four and a half, you don't notice at all. You absorb it.

So here's the part I can't answer for you. Who is currently absorbing the gaps in your work? Somebody is. If you can't name them, it's probably you, and you've stopped noticing.

  1. Signals

    Long form. One question or pattern, worked through.

  2. Signal Notes

    Short. Things I notice while staying close to the work.

  3. Signal Sessions

    Conversations, when talking is worth more than writing.

Where do you want to look?