Starting fresh

This is post number one. The blog is empty except for this, and that's intentional.

I've been sitting on this domain for a while, planning to fill it with architecture and visualization content: Blender tutorials, architectural design workflows, and all the stuff I know how to do. But every time I'd open the Ghost editor, I'd stare at the blank page and feel... nothing. No energy, no excitement, and a complete lack of will to even start it.

So I'm starting over, in a completely different direction. This time following what actually has energy and momentum.

Where the Energy Went

I've worked in architecture and visualization for 15 years. Designed spaces, created cool renders, and helped clients and friends to see projects before they existed. For most of that time, I loved it. But somewhere during 2025, that changed.

It wasn't dramatic. I still had a lot of contacts from "potential clients," but most of them were just people wanting a dream mansion but only having the budget to build a small cabin. Weeks would pass without a real project inquiry. I'd open Blender and just... not care. The ideas for personal projects were flowing, even more than at other times, but suddenly the will and excitement were just gone. I was going through motions instead of following momentum.

Meanwhile, I'd been doing web design work at my wife's digital marketing agency. She had a lot of requests for websites and needed someone who could build them. It started like that, but after a couple of months I was also writing newsletters, doing graphic design, and handling most of the tech maintenance and anything software-related. Not what I envisioned as a career, but it pays the bills. And in that work, something started stirring. Something I'd buried more than twenty years ago.

Going Back to Code

When I started university in 2004, I enrolled in computer engineering. I was really excited about it because since I was a kid, I've been completely obsessed with technology and computers. My dream was to build things with code, solve problems, and make tools that would help other people. But a few months in, I dropped out. That degree was totally obsolete, with a curriculum that looked like it was created in the early '90s. At that time it was impossible to switch to another course or university, so I just went home.

The following year, after much consideration, I switched to architecture. I told myself I made the right choice. Architecture was creative, tangible, and made sense. And for a long time it did. But by the end of 2025, I kept thinking: what if I'd stuck with it? What if I'd learned to code back then? What would I be building now?

So I decided to find out. I bought three online courses and committed to learning properly this time.

What I'm Learning

Right now I'm working through three courses by Jonas Schmedtmann. I researched a lot, and overall, his courses were highly recommended and were the ones with the best reviews.

The Complete JavaScript Course 2025: From Zero to Expert! - JavaScript fundamentals, everything from basics to advanced concepts

Node.js, Express, MongoDB & More: The Complete Bootcamp - Backend development and server-side JavaScript

The Ultimate React Course 2025: React, Next.js, Redux & More - Modern frontend development with React and its ecosystem

I'm not rushing it. Taking time to actually understand instead of just copying the code. Building small and basic projects as I go. Making mistakes, a lot of them!

The architecture background helps in some ways. Thinking in systems, managing constraints, and understanding how pieces fit together. All that resembles. However, the syntax, the logic, the debugging? That's all new muscle memory.

What Comes Next

Honestly? I'm figuring it out as I go.

I'm interested in building small tools (at first). Free and open-source tools. The kind of tools that solve problems I actually have. Maybe something to help my wife at her agency. Or something to help architects to organize their work and be able to seamlessly share it with partners or clients. Honestly, I've been having some ideas, but that's not my main concern at the moment. Time will tell.

The only thing I know is that everything will be open-source. That's something that really matters to me.

I'm inspired by people like John O'Nolan (the founder of Ghost), which is currently building Alcove. He's someone who builds in public, prioritizes RSS over algorithms, and makes things that respect users. That's the approach and philosophy I want to follow.

Some of this will work. Most won't. I'll document both.

What This Blog Becomes

Not architecture tutorials. That version never launched, and I'm relieved.

This is my public digital workshop now. My learning notebook, where I document:

• Progress on courses and projects
• Things I'm building (even small experiments)
• Tools I'm discovering
• Mistakes I'm making
• The actual experience of pivoting careers at 42 years old.
• Some personal reviews about tools and software.

I'll probably also write about other stuff occasionally, like sci-fi, retro games, 3D printing, and updates on building my homelab. Whatever feels relevant. I want this to be an open space, a window to the world, not a closed place focused only on one subject.

No fixed schedule. I'll write when there's something worth sharing. Could be weekly, twice a month, or even daily. Depends on the momentum. The most important thing now is to focus on learning how to code and not how to be a "pseudo-blogger."

Following the Energy

That's what this is about. Following the energy instead of obligation. Building things instead of waiting for clients. Learning in public instead of pretending I know more than I do.

I don't have a twelve-month plan or a content strategy. Just curiosity and commitment to at least try to show up consistently.

If you're interested in following along, learning to code, indie web tools, or building in public, subscribe. RSS or email, your choice. No spam, no tracking.

Thanks for being here at the start.

May The Code Be With You! 🚀

PS: I'm still figuring out the design of the website, so probably in the next couple weeks, there will be some visual changes (I'm also figuring that out as I go).