JonCameron Johnson

Make the next step smaller

Sun, 06 Sep 2026 00:00:00 GMT

A useful next step leaves something behind: a paragraph, a drawing, a question sent to someone who can answer it. “Work on the idea” leaves too much to decide when you finally sit down.

Consider the difference between starting a website and writing the first sentence someone will read on it. The website includes dozens of decisions. The sentence gives you one thing to inspect. Is it clear? Does it sound like you? Would someone know why they should keep reading?

That small piece can reveal what the larger project needs.

Small enough to finish, real enough to teach you

There is a trap here. Rearranging a task list can feel like progress because it is easy to complete. A useful small step touches the actual work. If you want to write, write a rough paragraph. If you want to build, make one part respond to an input.

Try ending a work session by leaving a specific instruction for the next one: “Rewrite the opening example so it fits in three sentences.” Tomorrow starts with a decision already made.

The larger ambition can stay large. The action in front of you only needs to be clear enough to do and substantial enough to learn from. That is also the point of thinking in models: reduce the thing until you can work with it.

Attention is a design decision

Sat, 05 Sep 2026 00:00:00 GMT

Before choosing colors or adjusting spacing, decide what someone should notice first. That decision gives the rest of an interface a purpose.

A page can contain several useful things and still be hard to use. A bright badge, a moving illustration, and three equally prominent buttons may each look fine on their own. Together, they ask the visitor to sort out your priorities.

Read the page as a sequence

Imagine someone opening an article. They need to recognize the subject, decide whether it answers their question, and begin reading. The title, description, and opening paragraph can do that work in order.

Now place an unrelated promotion between the title and the first sentence. It might be a reasonable offer, but its position interrupts that sequence. Moving it below the article could make both the reading and the offer feel more considered.

Try a short review: name the first three things you notice, then compare them with the first three things the visitor needs. Wherever those lists differ, you have a concrete design question.

Sometimes the fix is stronger contrast. Sometimes it is more space or a shorter label. Sometimes the element can disappear entirely. The right adjustment follows from the task. For a related question about what happens after that first impression, see build for the second use.

Build for the second use

Fri, 04 Sep 2026 00:00:00 GMT

When reviewing a product idea, imagine someone returning tomorrow. They already understand the promise. What can they get done now, and how easily can they pick up where they left off?

This question changes which details deserve time. The opening animation matters less than whether the previous project is easy to find. A clever empty state gives way to the ordinary experience of editing something that already exists.

Walk through a repeat task

Take a tool for preparing a weekly report. The first run might guide someone through choosing a source and arranging a few sections. On the next run, they probably want to reuse that structure with new information.

If every visit starts from scratch, the product keeps charging an introduction cost. A saved report, a clear date, and an obvious way to make the next version may be more valuable than another onboarding screen.

Write down one repeat task before adding another feature. Start from the state the user actually left behind. Include small interruptions: an unfinished edit, a missing source, a change of mind.

This is a useful design exercise, not proof that people will return. That still needs to be observed. But it gives the product a chance to be useful when they do. Attention is a design decision offers another way to inspect that everyday experience.

Leave room to change your mind

Thu, 03 Sep 2026 00:00:00 GMT

A practical way to examine an opinion is to write down what would change it. If the answer is “nothing,” it is worth asking whether you are still investigating the question.

This does not require treating every possibility as equally plausible. You can hold a strong view and describe the limits of the evidence behind it. The useful distinction is between how confident you feel and what your confidence rests on.

Give the belief a boundary

Suppose you think a simpler version of a product will serve its customers better. Write the claim precisely: “For someone completing this one task, removing these options should make the process easier.”

Then name the observation that would count against it. Perhaps people regularly need one of the removed options, or the simpler flow forces them into a workaround. Now a disagreement has somewhere concrete to go.

Without that boundary, “simpler is better” can explain every outcome you already prefer. With it, the idea becomes something you can test and revise.

The same habit helps with a personal plan or an argument in an essay. Keep the claim, its reasons, and its limits close together. A revision then becomes a change to a particular piece of reasoning. It does not have to become a judgment on the person who held it. That is one reason to keep your models visible.

The work between ideas

Wed, 02 Sep 2026 00:00:00 GMT

An idea often arrives with a feeling of completeness. You can picture the finished essay or the useful little tool. The missing parts become visible when you try to make it.

That first rough version is valuable precisely because it disappoints you in specific ways. The explanation skips a step. The interface assumes information the person does not have. The example sounds convincing until you work through it.

Leave yourself something to return to

Instead of keeping an idea as a title in a notes app, give it a small first form. Write the explanation, sketch the sequence, or describe an example from beginning to end. Then come back to it with one question: what does this need next?

For an essay, the answer might be a better example. For a tool, it might be a way to recover from a mistake. A focused revision is easier to judge than a vague promise to make everything better.

There should also be room to stop. If the rough version exposes a weak premise, you can keep the lesson and let the project go. Finishing every idea is an expensive rule to live by.

The habit worth practicing is returning with enough attention to make a decision. Keep going, change direction, or set it aside. If returning feels difficult, make the next step smaller.

Thinking in models

Wed, 01 Jul 2026 00:00:00 GMT

When I want to understand something complicated, I don’t start by reading harder. I start by drawing.

A model is a deliberate simplification. You throw away almost everything about a thing and keep only the few parts that matter for the question you’re asking. That sounds like cheating. It’s actually the whole trick. The real thing has too many moving parts to hold in your head at once; a good model has exactly as many as you can reason about, and no more.

Take a black hole. The full description is general relativity — field equations most people, including me, can’t solve by hand. But there’s a model hiding inside the math that anyone can hold: the event horizon. Picture a boundary in space with one rule. Cross it going in, and no path leads back out, not even for light. That’s it. You don’t need tensor calculus to reason with that picture. You can ask real questions and get real answers. Why is a black hole black? Because light that crosses the horizon can’t return to your eye. What happens as you fall toward it? The paths back out get narrower until there are none. The model doesn’t replace the math — it makes the math worth learning, because now you know what it is describing.

Here’s the shape of what I mean:

The arrow in the middle is where all the work happens. Choosing what to discard is the hard part, and it’s a skill you build by doing it badly a few times first. Keep too much and the model is as confusing as the original. Keep too little and it lies to you. Every model is wrong in some corner, and knowing where yours breaks is part of using it honestly.

This is most of what this blog will be. I take something that feels too big to grasp — a piece of technology, a market dynamic, an idea from philosophy — and I look for the small picture hiding inside it. Sometimes I get it wrong and have to redraw. That’s fine. A wrong model you can see beats a correct one you can’t.

If you can draw it, you probably understand it. If you can’t, you probably don’t yet.

Hello, world: why I'm writing here

Sun, 28 Jun 2026 00:00:00 GMT

I’ve meant to start writing for years. Something always got in the way — usually the feeling that I had nothing finished enough to say. So this is me getting over that.

I’m JonCameron. I’m a learner first, and a builder and architect after that, though the three tend to blur together. I’m curious about almost everything: how the world works, how the universe works, and how the small strange machines we call software fit inside both. That curiosity doesn’t switch off, and after enough years of it filling up notebooks and browser tabs, I decided it should live somewhere I can actually revisit.

A bit about me. I spent a chunk of my life as a competitive gamer, which taught me more about focus, losing well, and getting better on purpose than any classroom did. These days I’m more likely to be reading about astrophysics — black holes especially, which I find genuinely hard to stop thinking about. I love films made with care, and music that rewards a second listen. None of that is a career. All of it shapes how I think.

So what is this blog? It’s me thinking out loud. Some posts will be essays — arguments I’m working out, questions I don’t have clean answers to yet. Others will be models and diagrams, my favorite way to make a complicated thing hold still long enough to understand it. The topics will wander across technology, business, philosophy, and the plain work of becoming a better person. I’m not planning to stay in one lane, because my curiosity doesn’t.

I’m writing partly for anyone who finds it useful, and partly because writing forces a kind of honesty that thinking alone never does. If a diagram is wrong, drawing it shows me. If an argument is thin, writing it down thins it further until I either fix it or drop it.

That’s the whole idea. No grand schedule, no theme of the week — just the good stuff I’m chewing on, written plainly, one post at a time. Thanks for reading. Let’s see where it goes.