Translation note: This article was originally written in Spanish and translated into English with the assistance of AI. I reviewed and edited the final version to preserve the original meaning and tone.

So, what have I been doing all this time?

It has been almost six months since I last published anything here.

My last post was about what my MBA was teaching me beyond the syllabus. Ten courses in, I tried to put into words how that experience was changing the way I thought about product, strategy, business, and technology.

A lot has happened since then.

First: I finished the MBA.

And perhaps I should have written about it. About closing that chapter, what I learned, what was worth it and what wasn’t. Also about whether studying for an MBA as a software engineer changes — or doesn’t change — the way you understand your work.

But I didn’t.

Not because I ran out of things to say. Quite the opposite.

The problem with wanting to do everything

I have too many interests.

Software engineering. Artificial intelligence. Product. Design. Business. Investing. Knowledge systems. Building things. Understanding how they work. Taking them apart. Putting them back together.

And when something interests me, I rarely manage to stay on the surface.

So these past few months have been a fairly accurate representation of how my brain works: too many tabs open, too many ideas, and too little time.

I’ve started projects.

Abandoned some.

Put others on hold.

Returned to things I’d wanted to do for a long time.

And, while writing this, I’m probably already thinking about another one.

For a long time, I saw that dispersion almost as a flaw. The constant feeling that I should choose one thing, build a single brand around it, and repeat the message until the algorithm — or someone — decided to pay attention.

But the truth is, I don’t work like that.

I never have.

And perhaps it’s time to stop pretending otherwise.

I finished the MBA. And kept looking for more

This year, I finished my MBA.

It was an important chapter, but strangely enough, reaching the end didn’t make me want to stop. Quite the opposite.

I was left with more questions.

More desire to build.

More curiosity about what happens when you genuinely bring technology, product, strategy, and business together. Not as isolated disciplines, but as parts of the same system.

I suppose that, if I had to summarise what has changed in me during this time, it would be something fairly simple: I want more.

More knowledge. More autonomy. More ability to build my own ideas. More room to experiment. And more opportunities to discover how far I can go if I stop limiting myself to thinking about them.

I bought a PC to build

Yes, this deserves its own section — or perhaps an entire post.

After years of working mainly on laptops (and not having a personal computer of my own), I bought a desktop PC. Not exactly for gaming — although I’m not going to pretend that possibility doesn’t exist — but as a machine for my personal projects and AI experimentation, powered by an RTX 5070 WindForce OC SFF with 12 GB of GDDR7.

It may sound like an absurdly specific detail for a post like this, but it represents one of the decisions I’ve made over the past few months: I want to rely less on imagining and more on testing.

Run models.

Experiment locally.

Break things.

Build prototypes.

Better understand what is actually happening underneath all those interfaces promising to add “AI” to every product.

I don’t want to limit myself to consuming this transformation from the outside.

I want to get my hands dirty.

I’m also rebuilding my second brain

Another small obsession of mine has been my personal knowledge system.

For years, I’ve accumulated notes, ideas, references, projects, lessons, and documents. The problem is that accumulating information doesn’t necessarily mean being able to use it.

So I built a “second brain”. Now I’m in the middle of migrating, reorganising, and rethinking almost everything around it.

This isn’t just about having pretty notes or the perfect folder structure. What I’m trying to build is a personal infrastructure that better connects what I learn with what I do.

Research.

Ideas.

Projects.

Decisions.

Content.

Experiments.

Knowledge.

Everything is part of the same system.

Or at least that’s the theory.

In practice, as always, it involves broken links, structures that seemed brilliant three weeks ago, and the permanent suspicion that I may simply be procrastinating in an extremely sophisticated way.

00-lab

Of all the projects I’m involved in, one is starting to take on a particularly important shape. It’s called 00-lab. An AI Product Lab.

The idea is easy to explain and much harder to execute: build and validate AI-powered digital products using LEAN methodology.

I don’t want it to become a collection of abandoned side projects on GitHub.

Nor an excuse to add a chatbot to everything.

The goal is much more concrete: validate and launch at least one AI-powered product that demonstrates real traction.

Users.

Usage.

Interest.

Revenue.

Some signal that exists outside my own head.

I started this journey with Paperclip, and I’m now shipping Meeting Cost Ticker, a product that turns something as abstract as “the cost of a meeting” into something visible and tangible while it happens.

And there are more ideas.

Too many, obviously.

But that’s precisely why 00-lab is also an experiment on myself: on my ability to move from idea to validation, from validation to product, and from product to something someone actually wants to use.

I started investing again

This year, I also started investing again.

Not just saving. Investing deliberately.

After a period with other priorities, I resumed building my portfolio and started thinking seriously about the long term again.

This is also part of an idea that has become increasingly important to me: autonomy isn’t built solely by learning more or earning more.

It’s also built by creating margin.

Financial margin.

Time margin.

Room to choose.

I’m still a long way from financial freedom, but I’m moving in that direction again.

And that matters.

I changed physically too

Perhaps this is one of the most visible changes.

During this time, I’ve also worked on myself physically.

Not as something isolated from everything else, but as part of the same chapter.

Training.

Becoming more consistent.

Changing habits.

Seeing results.

Discovering that many of the things we’ve intellectually understood for years only start to matter once we manage to repeat them for long enough.

It hasn’t been perfect.

None of this has.

But there has been change.

And I think I needed to see it.

A thousand other projects

Of course, that’s not everything.

There are more projects.

More experiments.

More documents.

More repositories.

More ideas that will probably never go anywhere.

Some things are still too early to talk about. Others may not even survive until next month. And some have been quietly growing while I try to understand what I actually want to do with them.

I don’t want to turn this post into an endless list.

Among other things, because the problem has never been finding things to do.

The problem has been finding the time to talk about them.

Building and sharing are two different jobs

This is probably the main reason I’ve gone so long without publishing.

Building something takes time.

Learning takes time.

Working takes time.

Studying takes time.

Research takes time.

But sharing all of it takes time too.

Writing a post.

Preparing a publication.

Maintaining a social presence.

Thinking about formats.

Editing.

Publishing.

Replying.

Being consistent.

For a long time, I’ve tried to find the perfect system to do all of it.

Spoiler: it doesn’t exist.

And while trying to figure out how to publish consistently, I stopped publishing.

So I want to try something different.

Less perfection.

Less pressure to turn every idea into “content”.

Less need for a perfect strategy before saying anything.

And more sharing the process while it happens.

I’m back

I don’t know whether I’ll manage to publish every week.

Probably not.

I’m also not going to promise an impossible schedule that I’ll abandon two months from now.

But I do want to write again.

I want to share more about artificial intelligence, software engineering, product, technology, knowledge systems, investing, and the things I’m building along the way.

I want to document the experiments behind 00-lab better.

I want to talk about what works.

And what doesn’t.

I want this space to become more than somewhere I publish a reflection every six months when I somehow manage to find three free hours.

Because I still believe in something that probably explains much of everything above:

learning is better when you build, and building is better when you share.

So yes.

I’m back.

And, as always, I have too many things going on.

This time, I’ll try to tell you about them.

---

💡 What are you working on?

If you’re also building something, learning a new skill, experimenting with AI, or trying to keep far too many projects alive at once, I’d love to hear about it.

Leave a comment and tell me:

What are you building right now?

And if any part of this post felt familiar, share it with that person who also lives with far too many tabs open. 🚀