You Can Just Do Things

Most of the things I want to do become harder when I turn them into a plan for becoming ready.

I tell myself I need a better idea, more knowledge, more confidence, or more proof before I begin. Then preparation becomes the thing I do instead of the thing that helps me start.

The truth is simpler: you can just do things.

You can start the project, publish the post, send the message, or make the thing before you know whether anyone will care. Most people are too busy with their own lives to care about your first attempt.

Preparation can become avoidance

A lot of ambition gets trapped inside preparation. You decide to build a company, so you research fundraising, hiring, positioning, market size, pitch decks, and the perfect technology stack. You decide to learn to code, so you compare courses and list everything you need to understand first.

These activities can be useful. They can also become a convincing way to avoid the actual thing.

The real work is usually less impressive:

• open the editor
• write the first line
• make the ugly version
• ask someone what they think
• fix what does not work
• do it again

Preparation feels safe because it lets you imagine progress without creating evidence.

I waited to feel ready

When I started coding, I thought I had to understand everything before I could build anything real. I watched tutorials, learned concepts in isolation, and built small projects by following instructions.

That moment of readiness never arrived. There was always another framework, concept, or part of the stack that seemed important. If I kept waiting, I could stay a beginner forever while feeling productive.

The first time I made something I actually wanted to use, I still did not know what I was doing. I used AI for parts of it, searched through documentation, made bad decisions, and broke things that had been working five minutes earlier. But I had crossed an important line.

I was no longer preparing to become someone who builds things. I was building things. Every gap in my knowledge became connected to a real problem, which made learning much more direct.

The first version is allowed to be bad

Starting does not mean committing to the final version. The first website can look bad, the first product can have three users, and the first essay can be awkward.

The first version is not a verdict on your ability. It is an instrument for finding out what you do not know yet.

The bad first version is useful if it gives you a clearer second version. The only truly wasted version is the one that stays inside your head forever.

The first version is not a verdict. It is evidence.

Nobody is coming to give you permission

The internet cannot remove every constraint. Money, time, school, health, and family responsibilities matter. But the cost of trying has fallen dramatically.

You do not need to live in the right city to learn from people there. You do not need a large audience to publish an idea. You do not need a company behind you to make a useful tool.

I started learning about software and startups before I had access to the people or places I associated with them. The internet gave me a way to practice before I felt like I belonged there.

Belonging usually comes after participation. You do not wait until you feel like a builder, writer, founder, photographer, or athlete. You do the activity, and the identity slowly becomes harder to deny.

Action creates evidence

When you are stuck, your thoughts become unreliable. You think your idea is bad, but you have not shown it to anyone. You think nobody will care, but you have not asked them.

I learned this while building Ryva. You can spend a long time improving the architecture and making the interface cleaner, but none of that answers the most important question: does this solve a problem someone cares enough about to use repeatedly?

A conversation can answer more than a week of speculation. A rough demo can expose a better direction than a perfect internal plan. A real rejection can be more useful than a hundred imagined objections.

The goal of action is not to prove that your first idea is correct. It is to replace guesses with information.

That is why shipping matters even when the result is small. It gives reality something to respond to.

Just do things does not mean do everything

You still need judgment. Some projects should be abandoned. Some opportunities are distractions wearing the clothes of possibility.

Doing things is not the same as moving constantly. It means choosing an action that can teach you something and taking it before you have created ten reasons not to.

When I am stuck, I ask:

1. What am I waiting for?
2. Is that requirement real, or does it only make me feel safer?
3. What is the smallest version I can do today?
4. What result would tell me what to do next?

Build the smallest version and put it in front of someone. Write one honest page instead of designing a personal brand. Pick one resource and use it to make something instead of collecting more resources.

The action does not need to guarantee success. It only needs to make the next decision easier.

Start before the story makes sense

Looking backward, my path seems more intentional than it felt while I was living it. Coding led to projects, projects led to more skills, and those skills led to larger products. At the time, most of those steps were just experiments: trying a tool, fixing a bug, reading documentation, or starting something that might fail.

None of those actions came with proof that they would become important later. That proof only appeared after I moved. You need enough direction to know what is worth trying, not a complete map of where it will lead.

The plan gets clearer after contact with reality, not before.

You can just do things

This is how most real work begins. Someone notices a problem and tries to solve it. Someone has an idea and writes it down. Someone wants to become stronger and goes to the gym.

They do not become ready first. They become ready by doing the thing repeatedly, paying attention, and improving the next version.

You do not need the perfect university, mentor, investor, team, audience, or idea to begin. Those things can help later, but they are not prerequisites for making the first attempt.

Make the project. Publish the thought. Ask the question. Then let reality answer.

Open the document, do the small version today, and remember that you can just do things.