Notes

Things I don’t want to forget.

Some ideas arrive while building. Some come from work, conversations, books, mistakes, or simply changing my mind.

I keep notes because thinking changes quickly. What feels obvious today may look completely different after another hundred conversations, another product iteration, or another environment.

This is not a collection of final answers. It is a record of ideas I thought were worth keeping.

Building · Learning · Systems · People · Life · Changed My Mind · Quote Notes

Pinned Note

The problem deserves loyalty.
The first idea does not.

One of the hardest things about building is separating the problem from the solution you became emotionally attached to.

When I first started thinking about student guidance, I believed mentorship was the answer. Then information. Then summaries. Then tools. Then AI-assisted guidance.

Each version made sense at the time. And each version became less important when reality showed me something deeper.

I used to think changing the model meant losing direction. Now I think the opposite. You can stay deeply committed to the question while being completely willing to change the answer.

That is not inconsistency. That is learning.

BuildingChanged My Mind

Thoughts I keep returning to

Building

Ambition needs compression.

A big vision can be useful because it shows what might eventually be possible. But a big vision is not automatically a good first product.

At one point, I had around 40 ideas, tools, and systems mapped around the student journey. Everything felt important. That was exactly the problem.

Simplification is not the same as thinking smaller. Sometimes the most ambitious thing you can do is decide what not to build yet.

People

Environment changes what feels possible before it changes what you can do.

Being around ambitious people does not instantly make you more skilled. But it changes your reference point.

You do not always need to be the most capable person in the room. Sometimes you need to be in a room that forces you to become more capable.

Learning

Learning becomes faster when there is something real at stake.

I have learned from courses, books, videos, and classrooms. But the fastest learning usually happens when I am trying to solve something real.

Real problems expose the exact gap between what I think I know and what I actually know. That gap is usually where the learning begins.

Systems

What users see is often the smallest part of the system.

A product can look simple on a screen. Behind it may be people, operations, data, incentives, policies, trust, distribution, support, and hundreds of decisions the user will never see.

The interface is often only the visible edge of something much larger.

Building

Shipping is useful when it creates information.

Speed by itself is not impressive. Building quickly only matters when it helps you learn something that thinking alone cannot reveal.

Sometimes a rough product that exists creates more truth than a perfect product that is still being discussed.

Product

Communication is part of the product.

A product may be much deeper than the way people initially perceive it. But perception still matters.

If people misunderstand what you are building, they will compare it with the wrong alternatives, ask the wrong questions, and judge it through the wrong category. That is not only a marketing problem — it may also be a product problem.

Good communication helps people form the correct mental model before they decide whether something is valuable.

Changed My Mind

Where my thinking moved.

01 · GuidanceRevision
I used to think

Students need better mentors. Mentorship felt like the most human answer — someone who had already gone through the journey could guide someone who had not.

What changed

Mentors have limited time. Quality varies. Context gets lost. Students need help continuously, not only during occasional conversations.

Now I think

Mentorship can be valuable, but navigation needs a system. A person can help with a moment. A system can preserve context across the journey.

02 · InformationRevision
I used to think

Students need better information — more websites, videos, groups, counselors, agencies, AI, and seniors.

What changed

Students already had more information than they could reasonably process. The problem was not finding another answer — it was understanding which answer mattered for their situation.

Now I think

Access is not the same as clarity. The next generation of useful systems may not win by producing more information. They may win by understanding context better.

03 · BuildingRevision
I used to think

A larger product meant a stronger vision.

What changed

More features created more complexity. The product became harder to explain, harder to use, and harder to build.

Now I think

The strongest first product may be the smallest expression of a very large idea. Focus is not a lack of ambition — it is how ambition becomes executable.

04 · CareerRevision
I used to think

Choosing a field meant staying inside one lane.

What changed

Building a technology company exposed me to problems in technology, business, behavior, operations, markets, trust, distribution, leadership, and organizations. No single label explained what I needed to learn.

Now I think

Careers can be built around accumulating capabilities, not protecting labels. The question I care about more is: what will this environment help me become capable of doing?

Short notes

Note · Career

A title tells you where someone worked. It does not tell you what changed because they were there. That is why I care more about contribution, learning, and capability than titles alone.

Note · Building

Sometimes leadership means removing the bottleneck yourself. Not because you should do everything forever. Because sometimes waiting costs more than learning.

Note · Systems

The best question is often one level deeper than the one everyone is answering. Students asked for mentors — the deeper need was clarity. They asked for information — the deeper need was direction. They asked for tools — the deeper need was coordination.

Note · Product

Progress becomes more valuable when it can be reused. A document created once. An achievement recorded once. A decision understood once. Why should the next system start from zero?

Note · Learning

I would rather discover that I was wrong early than defend being wrong for a long time. Feedback can hurt the ego. Silence can hurt the product more.

Note · Life

The person needed for the next chapter may require skills I do not have yet. That does not make the chapter impossible. It tells me what I need to learn.

Note · Building

Recognition is useful when it creates momentum, not identity. Awards can open doors. They cannot do the work that comes after the door opens.

Note · Life

Being young means I have less experience. It also means I still have a lot of time to compound what I learn. I would rather use that as motivation than pretend the experience gap does not exist.

Quote Notes

A short idea. Why I saved it.

The only true wisdom is in knowing you know nothing.

Attributed to Socrates

Why I saved this

The more I learn about startups, products, AI, organizations, and markets, the more obvious it becomes how much I still do not understand.

I used to think expertise meant reaching a point where uncertainty disappeared. Now I think serious learning often makes uncertainty more visible.

Not knowing is not the problem. Pretending to know can be.

Well begun is half done.

Aristotle

Why I saved this

I do not interpret this as “start quickly and everything becomes easy.” For me, it means that defining the problem correctly changes almost everything that follows.

A team can execute brilliantly against the wrong problem. A product can be beautifully designed around the wrong assumption.

Starting well often means spending enough time asking: what are we actually trying to solve?

Current Questions

Things I’m thinking about now.

Questions I don’t have complete answers to yet.

  1. 01

    How should AI remember people over long periods without becoming intrusive?

    Personalization becomes much more useful when a system understands history. But persistent context also creates questions about trust, control, privacy, and what should be forgotten. I think this will become one of the most important product-design questions in AI.

  2. 02

    What makes someone return to a system before they urgently need it?

    Many educational products are used only when a deadline appears. But long-term readiness requires behavior before urgency. How do you create value early enough that preparation becomes a habit?

  3. 03

    How do you build trust before you have scale?

    Large organizations inherit some credibility from their history. New companies do not. For something involving education, money, documents, and a student’s future, trust cannot simply be assumed. How much comes from product quality, people, partners, institutions, transparency, evidence? I am still learning.

  4. 04

    What should humans remain better at even when AI becomes extremely capable?

    AI can increasingly generate, analyze, recommend, summarize, and automate. But I am interested in what becomes more human, not less valuable, as AI improves. Judgment? Trust? Responsibility? Taste? Relationships? Leadership? Knowing which problem is worth solving? I do not know yet.

Recently Learning

What I am actively studying.

Product Systems

How products preserve context across long user journeys.

AI

Memory, personalization, agents, cost, trust, and real-world workflows.

Distribution

Why useful products still fail to become habits.

Operations

How execution changes when many people and processes depend on each other.

Leadership

How ownership, standards, trust, and accountability work inside teams.

All notes

12 of 12
Changed My Mind

Mentorship was not the problem.

I started by thinking students needed access to the right people. What I eventually learned was much more complicated.

JUL 2026 · 4 MIN
Building

Ambition needs compression.

Forty ideas mapped around the student journey. Everything felt important — which was exactly the problem.

JUL 2026 · 3 MIN
Building

Shipping is useful when it creates information.

Speed by itself is not impressive. It only matters when it helps you learn what thinking alone cannot reveal.

JUN 2026 · 2 MIN
Product

Communication is part of the product.

If people misunderstand what you are building, they compare it with the wrong alternatives and judge it through the wrong category.

JUN 2026 · 3 MIN
Systems

What users see is often the smallest part.

The interface is often only the visible edge of something much larger — people, operations, data, incentives, trust.

JUN 2026 · 2 MIN
People

Environment changes what feels possible.

Sometimes you need to be in a room that forces you to become more capable, not the room where you are already the most capable person.

MAY 2026 · 2 MIN
Career

Careers around capabilities, not labels.

The question I care about more is: what will this environment help me become capable of doing?

MAY 2026 · 3 MIN
Learning

Learning becomes faster when something is at stake.

Real problems expose the exact gap between what I think I know and what I actually know. That gap is usually where the learning begins.

MAY 2026 · 2 MIN
Life

Recognition is useful when it creates momentum.

Awards can open doors. They cannot do the work that comes after the door opens.

APR 2026 · 1 MIN
Quote Notes

The only true wisdom is in knowing you know nothing.

Serious learning often makes uncertainty more visible. Not knowing is not the problem — pretending to know can be.

APR 2026 · 2 MIN
Quote Notes

Well begun is half done.

Defining the problem correctly changes almost everything that follows. Start by asking what we are actually trying to solve.

APR 2026 · 2 MIN
Changed My Mind

Access is not the same as clarity.

Students already had more information than they could reasonably process. The problem was understanding which answer mattered for them.

MAR 2026 · 3 MIN
A small disclaimer

These are snapshots of my thinking, not permanent positions.

Some notes may age well. Some probably will not.

I hope that, years from now, parts of this archive show me things I once misunderstood. That would mean I kept learning.

I would rather leave evidence of changing my mind than pretend I was always right.

Some thoughts are useful. Some are just worth remembering.

I started keeping notes because ideas disappear surprisingly fast. A sentence from a conversation. Something I understood while building. A mistake I do not want to repeat. A question I still cannot answer.

Maybe this page becomes a record of how my thinking changes over time. For now, it is simply where I keep the things I do not want to lose.