Bits and Bobs 1/26/2026

The self is not a state, it's a limit. You never arrive, but with enough signal the system can get meaningfully closer.

To move in that direction, identity can't be declared upfront. It has to emerge from what you repeatedly do, choose, return to and abandon.

That only works if the data coheres. Accumulation alone just adds noise; structure and context are what let meaning compound and eventually the system reflects something back that feels accurate.

Eventually, your Shelf actually becomes a mirror.

My reflex under pressure is to add effort instead of clarity.

More motion feels productive, but it reduces thinking space.

When I stay in the weeds, I trade leverage for activity.

I'm learning that stepping back is not disengagement. It's how focus appears.

We're used to money coming from two places: users, or people paying to influence users.

We assume ads are the inevitable shape of that second bucket because that's the last 20 years.

But ads are the most misaligned version: they monetize interruption at the exact layer that's getting most intimate.

The better endpoint is rails: infrastructure that moves context, permissions it, and makes it usable, priced like usage fees.

More pull than push. A toll to participate in user-authorized intent.

It's been 2 years since I did the Hoffman Process and one of my favorite simple tools is choosing the Left Road or Right Road as a way to identify habitual responses under pressure and the more constructive alternatives available in the same moment. It's interesting to apply this at work.

On a team, patterns come from multiple places. Individual habits compound, a leader's patterns magnify, and new collective patterns emerge through repeated interactions.

Left Road / Right Road helps surface destructive patterns early. Once a pattern is named, it becomes a choice instead of a default. Asking "What's our Left Road here, and what's the Right Road version?" creates a real-time reset and helps us course-correct in the moment.

I've been seeing more and more young people wear eye patches on camera and in public.

Like pimple stickers before them, they make care visible instead of invisible. Shifting the message from "I need fixing" to "I'm human and unbothered." They quietly signal effort, late nights, staying out. Almost a status cue.

They also lean into the new-found obsession with being nonchalant, because I "lowkey don't give a fah".

When do you go top-down vs. bottoms-up? It hinges on three variables: ambiguity, urgency, and the team's experience in this problem space. It's not a binary choice, but a sliding scale to move along as conditions change.

Directive: When the problem is hairy, poorly defined and time-sensitive. In these moments, convergence matters more than exploration. The job is to reduce ambiguity, set constraints, and create a tractable problem the team can execute against.

Bottoms-Up: When the problem is well-scoped and the team has demonstrated competence in this terrain. Here, over-directing slows things down. The work benefits from trusting the experts, local judgment, iteration and letting the shape emerge from doing.