Welcome

For a while I kept circling the idea of a site of my own. Not just a CV in HTML — a place to show what I can build and, at the same time, write down what I’m learning. I talked about it with people close to me. They pushed me to open it. So here it is: carlosdcorona.com.

A place to document the path

I work in data. A lot of what you’ll find here will have that tint.

I’ll write about Data Engineering, Analytics, AI, and the day-to-day problems: pipelines that break on Monday, architecture decisions that cost more than the slide suggested, things I understood late, tools that actually saved me — and tools I overrated.

I also want it to feel human.

I came into data from Physics Engineering. Then a first remote job with teams in other countries, a master’s, projects that worked and ones that didn’t. At some point I noticed something I was already doing: I could put the laptop in a backpack, change cities or countries, and keep working.

It sounds great. Often it is. It also has another face.

Remote is not vacation. Traveling while you work takes discipline. Time zones matter. Wanting to see a city when you have a call at four. Having all the freedom in the world and realizing you still have to learn how to use it.

That part belongs here too.

I’m not writing as if I have the manual

That’s the rule of this space.

I’m not building this because I think I’ve solved the perfect career, the ideal Data Engineer path, or frictionless digital nomad life. I’m still figuring several of those out.

What I do have are experiences, mistakes, questions, and lessons that might help someone on a similar path.

If something took me six months and I can make it clear in ten minutes, good. If a professional mistake keeps someone else from repeating it, better. And if in three years I reread a note and I was wrong, I want to be able to see that too. Documenting while the process is still happening is part of the point.

What can you expect here?

I don’t want to decide the full index on day one.

Some days will be a technical problem that had me spinning for a week. Others will be something I learned with a team, a decision that worked, or a mistake that forced a different way of thinking.

And there will be stories away from the desk: working from another country, a meeting in an awkward time zone, keeping a routine while moving, opening the laptop somewhere I never pictured working.

Some won’t be “life lessons.” They’ll just be what building a career like this looks like.

Over time, recurring themes will probably show up: how to get into and grow in data, working remotely with teams in other countries, the less glamorous parts of doing that —schedules, discipline, paperwork, balance—, technology, AI, ownership, travel, and whatever else crosses the path.

I’d rather discover those by writing than force every story into a label from day one.

What is carlosdcorona.com?

For now: portfolio and field notes.

You’ll find experience, systems I’ve worked on, projects, and what I know how to build. It’s also a space that’s mine: what I’m learning, what I care about, and what still makes me want to keep going.

Not only the technical layer — data, math, AI, pipelines — but how I see work, the curiosity that got me here, and what I still don’t know.

I don’t have the five-year roadmap. That’s fine. For now I want to write what’s worth the time, share what I’m learning, and document the path with a little more honesty than fits in a LinkedIn post.

If something here helps you, makes you think, saves you a mistake I already paid for, or makes you want to talk about it — then the site is already doing its job.

Welcome.