A long attempt at understanding myself.

I didn't do well in school.

Not because I didn't like computer science — in fact, I've always been interested in how systems work, how things connect, and how problems can be broken down and solved. But most of what I was asked to do in school didn't feel real to me.

Assignments were often self-contained, artificial problems. I could complete them, but I couldn't connect to them. I didn't feel a reason to care, so I didn't go deep.

After graduating, that changed.

In the real world, problems are messy, unclear, and have consequences. When something breaks, it matters. And for the first time, I found myself fully engaged.

I started using the same concepts I once ignored — but now with context, purpose, and urgency.

I realized I was never bad at learning. I just needed a real reason to learn.

I'm not driven by tasks or instructions. I'm driven by problems.

When I encounter something unclear or challenging, I naturally go deep. I explore different approaches, test ideas, and stay with it until it makes sense.

I don't enjoy doing things just because they need to be done. But I'm highly engaged when something needs to be understood.

When I'm engaged, I can focus intensely.

I can spend hours solving a problem, losing track of time, fully immersed. It's not discipline — it's natural.

But this only happens when the work feels meaningful.

If something is repetitive or disconnected from real outcomes, I struggle to even begin.

• When something matters → I go all in
• When it doesn't → I disengage

I'm very good at:

• Breaking down problems
• Designing systems
• Exploring solutions
• Building the core of things

But I struggle with:

• Repetition
• Polishing
• Finalizing
• Doing the same thing over and over

Once the interesting part is solved, my motivation drops.

I'm consistent in how I engage with problems — but not in how I stick to tasks.

I have a strong bias against repetitive work.

If I find myself doing the same thing more than a few times, I don't see it as something to tolerate — I see it as something that should be automated.

I don't like being inside the process. I prefer building the process.

I don't want to rely on constant effort.

If something only works when I'm actively involved, then I'm not building a system — I'm just maintaining it.

I prefer:

• systems that run
• flows that continue
• outputs that are generated consistently

Even if they start small.

A project is not done when the code works.

It's done when:

• it runs automatically
• it produces output
• it reaches real users
• it creates value

Until then, it's incomplete.

Two things matter.

• Real usage. Seeing something I built being used makes it real.
• Money. Money is a clear signal that something has value.

I don't see my work as isolated projects. I see them as evolving systems.

Deal Aggregation System — a system that collects, filters, and presents deals. The goal is not just to gather data, but to create a continuous flow of useful information that can reach users and generate value.

Automation Workflows — small systems I build to remove repetitive tasks, from data entry to content generation. They're not always visible, but they reduce manual work and make processes more reliable.

AI-assisted Pipelines — experiments using AI to enhance workflows: rewriting content, generating images, or transforming raw data into usable outputs.

Across all of these, the pattern is the same:

• identify a problem
• build a system
• reduce manual work
• move toward something that can run independently

I don't struggle with building things.

I struggle with finishing the parts that make them matter.

I'm actively working on:

• pushing systems into real use
• connecting them to users
• turning them into something complete

I work best when:

• there's a real problem
• I understand why it matters
• I have space to explore
• I can iterate

I may ask questions — not to challenge, but to understand.

I'm still figuring things out.

But I know this:

I don't just want to build things. I want to build systems that work — without me.