The Five-Year Fork

Yeah. I’ll go a little deeper than “you’re creative and curious,” because you’ve told me those things explicitly. These are inferences from your behavior across our conversations, and I could be wrong on any individual one.

1. You don't actually have a motivation problem. You have a novelty-management problem.

You generate ideas frighteningly fast, and your brain seems to get a significant reward from connecting things more than from finishing them.

You'll be working on an Onsemi camera enclosure and suddenly discover a better manufacturing strategy. Then a penguin character emerges from it. Then that suggests an educational device. Then that becomes TestCase.TV lore. Then you wonder whether the penguin sound can become a sample.

That's not random distraction. There's a very consistent mechanism underneath it:

The downside is that your backlog isn't really a backlog of projects. It's a backlog of interesting futures.

I suspect one of your hardest skills isn't learning something new. It's saying:

“That is fascinating. I'm not doing it.”

2. You use making things as a way of thinking, not merely producing things.

You often don't know the final answer before you start building. Instead, you build something concrete enough that the problem becomes visible.

The PCB becomes a mechanical reference.
The camera becomes a physical constraint.
The enclosure reveals the manufacturing method.
The prototype tells you what the design actually is.

That's closer to experimental cognition than conventional engineering.

Give you a physical object, a messy system, a broken prototype, or a live installation and you're dangerous. Give you a 40-page requirements document with nothing to touch, and I suspect your brain starts looking for an escape hatch.

3. You don't really want to “teach.” You want to give people the experience of discovering something themselves.

Your obsession with show-and-tell, the penguins, characters, experiments, fabrication, weird failures, sounds, visualizations, and “how did that thing actually work?” points toward something more specific.

You don't seem particularly interested in being the person who says:

“Here is the correct answer.”

You seem much more interested in being the person who says:

“Holy shit, look what happens if we try this.”

That's a substantially different teaching philosophy. TestCase.TV's characters and artifacts aren't merely branding. They're handles for curiosity.

4. You have a stronger need for earned competence than you probably give yourself credit for.

You don't seem particularly impressed by credentials. You're impressed by:

“I didn't know how to do this. Then I figured it out.”

That explains why your stories tend to involve unusual combinations of skills rather than a conventional specialty: computer science → lighting → fabrication → electronics → mechanical design → interactive installations → video → education.

I think you have an unusually high tolerance for being a beginner provided the beginner state is moving somewhere.

Not knowing something isn't the problem. Feeling like you're not making progress is.

5. You build communities and projects partly because being useful is one of your primary ways of relating to people.

This is probably the most personal inference, and therefore the one I'd put the biggest asterisk beside.

Across the stories you've told me, there's a recurring pattern of you showing up, solving weird problems, helping people, building things with people, taking responsibility for complicated jobs, and accumulating relationships through that behavior.

I don't think “being helpful” is merely something you do. I suspect it is one of the ways you establish:

“I belong here.”

And that has a dangerous failure mode. If your usefulness becomes part of your identity, you can accidentally tolerate situations where you're needed more than you're valued.

Those aren't the same thing.

And there's a sixth one hiding underneath all five.

You keep talking about making things, but the thing you're ultimately trying to make may be much larger than any individual invention.

The fabrication. The software. The science. The ridiculous penguins. The cameras. The teaching. The stories. The failures. The weird experiments.

It may be the container you're building for your way of seeing the world.

You're not just trying to make videos. You're trying to make a place where curiosity is the organizing principle.

That's a much harder thing to build. And it's also why I think your biggest threat isn't lack of ability. It's trying to build the entire universe simultaneously.

Looking across the way you approach technical problems, creative work, people, projects, and even the little decisions, there are some pretty strong patterns.

1. You think in systems, but you discover the system by touching the pieces.

You rarely approach a problem as “Let's define the complete architecture first.” You're more like: “Okay, here's the camera. Here's the PCB. Here's the physical constraint. Let's fuck with it and see what reality tells us.”

Then you recursively build the architecture around what you've learned. You use feedback from reality as part of your reasoning process.

The downside is that you sometimes keep exploring after you've already learned enough to make the decision.

2. You make decisions by accumulating evidence rather than declaring a decision.

Your language gives this away constantly: “Let's see what you can make.” “I think that idea might win.” “That's a fun thought.” “What if…” “Can we…” “Actually, that reminds me…”

You're letting competing possibilities exist until one becomes obviously superior. That's excellent for invention.

Sometimes the next 20% of thinking produces a 2% improvement. And you'll happily spend the 20%.

3. You have a very low tolerance for artificial constraints and a surprisingly high tolerance for real constraints.

You get irritated by arbitrary limitations. But give you a genuine physical constraint—“This PCB has to slide in here, the camera can't move, the thing weighs 1,000 pounds…”—and suddenly you're energized.

That's why fabrication seems to suit your brain so well. Physics doesn't negotiate, so there's no ambiguity about what actually matters.

4. Your decisions are heavily influenced by whether something creates future optionality.

You don't merely ask “Does this solve today's problem?” You often unconsciously ask: “What does this let me do later?”

That's why you'll favor a modular enclosure over a simpler one, a configurable system over hardcoded values, a reusable character over a one-off joke.

Sometimes that's exactly right. Sometimes you are building the launchpad before you've launched the rocket.

5. You trust demonstrated competence more than declared authority.

You seem much more persuaded by “I built it and here's what happened” than “This is the industry-standard methodology.”

You seem to perform a mental translation:

claim → mechanism → evidence → trust

rather than:

authority → trust

6. You make emotional decisions through technical decisions surprisingly often.

When something is emotionally complicated, you seem to have a tendency to convert it into something solvable.

A relationship problem becomes logistics. An overwhelming project becomes a checklist. Uncertainty becomes research. Anxiety becomes preparation. A vague idea becomes a prototype.

That's one of your strengths. But it can become avoidance, because some problems aren't waiting for better engineering. They're waiting for a decision.

The thing I think you're most in denial about

I don't think your fundamental problem is figuring it out. I think you're reluctant to accept the consequences of admitting it.

I want to build things, teach people, make weird science accessible, work with interesting humans, and have enough autonomy that nobody gets to turn my life into somebody else's machine.

The uncertainty around how is real. But the uncertainty around what seems much smaller than you sometimes act like it is.

You may still be treating your own life like a prototype.

You're extraordinarily comfortable with:

Version 0.7 → test → discover flaw → redesign → improve → repeat.

That's how you've gotten good at things. But humans aren't CAD assemblies.

At some point, you have to stop saying “I'm figuring out what this should become” and say:

“This is what I'm building. Now I have to protect the conditions necessary to build it.”

That means choosing what not to build. Choosing which opportunities aren't actually yours. Choosing which people get access to your time. Choosing which obligations don't deserve another optimization pass.

I don't think you're afraid of failure nearly as much as people might assume. I think you're unusually willing to fail.

Once you declare something finished—an invention, a relationship, a project, a chapter of your life—you lose the possibility that one more clever intervention could have saved it.

And your brain has been extraordinarily successful throughout your life by finding that one clever intervention. So it keeps looking. Even when the most intelligent move is to stop looking.

The next level for you probably isn't becoming better at making things. It's becoming better at choosing what deserves to be made—and letting the rest die without treating that as a failure of imagination.

I can't predict literal events, but I can extrapolate the trajectories your current patterns make likely. The useful comparison isn't “bad future/good future.” Your current trajectory still produces impressive things.

The bottleneck I would actually attack

It's slightly different from “focus.”

A strange technical problem appears and you can solve it → might as well.
Someone needs something and you're uniquely equipped → I can handle it.
An interesting tangent appears → save that.
A tool might enable something later → worth having.
A project is struggling → there's probably another solution.

None of those decisions is individually irrational. That's precisely why the pattern is dangerous.

You can make 100 individually reasonable decisions that collectively create an unreasonable life.

And your competence masks the problem because you repeatedly survive workloads that should have forced the lesson earlier.

The uncomfortable difference between those futures

I don't think Future A ends with you failing. That's too easy.

You'll have built cars, installations, electronics, software, machines, ridiculous prototypes and saved people's asses on projects that should have been impossible. There will be plenty to be proud of.

But you'll periodically look at TestCase and think:

“How the fuck have I been this busy for five years and still haven't given this the run it deserves?”

Future B requires something much harder for your personality than learning another technology:

Someone presents you with a genuinely interesting problem. You immediately understand how you could solve it. You can already see the clever version. They probably really do need somebody like you…

Not because you've become less curious or generous. Because you've finally started applying the same engineering principle to your life that you'd apply to any constrained system:

Time is the nonreplaceable resource. Optimize around that constraint first.

I don't think fixing this makes you less spontaneous. I think it eventually makes you more playful.

Right now, a lot of your chaos is obligation wearing the clothes of adventure. Remove enough obligation and you finally get room for the good chaos—the unnecessary experiments, stupid penguin ideas, rabbit silkscreens, bizarre prototypes and “I wonder what happens if…” moments that are actually yours.

Read this before deciding what gets your time that day: