Welcome to Ciberdata

This site was created as a space to document ideas, projects, and lessons learned around technology, data, and the building of digital products.

For years, I have worked close to systems, analytics, automation, and the development of solutions that connect business with technology. Still, many of those ideas, experiments, and reflections remained scattered across notes, repositories, scripts, and technical conversations. Ciberdata is meant to become a place where all of that can come together in one place.

What will you find here?

The goal of this site is to publish content that is useful, clear, and practical. Topics that will appear here include:

  • data engineering and automation;
  • experiments with Python, Docker, and Google Cloud;
  • digital analytics and measurement architecture;
  • small tools built to solve real problems;
  • ideas about products, systems, and scalability;
  • explorations around AI, content generation, and software-assisted workflows.

I am not interested in filling this space with generic writing. I want these posts to reflect real work: concrete problems, technical decisions, mistakes, improvements, and lessons worth keeping.

Why this site?

There is something important about building your own site: it forces you to structure your thinking more clearly.

It is not the same to solve something quickly on a local machine, leave behind a working script, or close a topic in a notebook, as it is to turn that experience into an explanation that someone else can understand, reuse, or challenge. That difference matters.

There is also a practical reason for this project: I want to build a digital base of my own, one that is portable and extensible, where I can publish everything from a simple landing page to deeper technical content, and eventually integrate tools, automations, or small products.

Where this can grow

Today, this project begins in a simple form, but it is designed to evolve.

The current foundation already separates frontend, content, and services, with the intention of growing toward things such as:

  • a Markdown-based blog;
  • automation for drafting and editing content;
  • internal publishing tools;
  • visualizations or interactive experiments;
  • small web products built on the same infrastructure.

I would rather begin with a structure that is simple, understandable, and maintainable than with a heavier solution from day one.

What comes next

This first post is only the starting point.

The next pieces will likely focus on the construction of this very site: Docker, deployment on Cloud Run, project structure, architectural decisions, and the way I intend to scale it without losing simplicity.

If this space accomplishes anything, I hope it does this: turn real technical work into knowledge that is structured, useful, and reusable.

Thanks for stopping by.