About

## bio

I'm Jorge Ferreira, a software engineer. Throughout my career, I've been building and evolving systems that people can understand and rely on, even as products, teams and contexts change. I write to record what I learn along the way.

Along the way, I've learned that the hardest part is rarely getting a system to work for the first time. The real challenge comes later: when new requirements show up, integrations turn out to be unexpected, business constraints shift, incidents happen, and the context behind old decisions starts to fade.

I'm especially interested in what happens when software needs to keep evolving without becoming fragile, opaque or hard to operate. How do you preserve the intent behind decisions? How do you manage complexity instead of just hiding it? How do you build systems that stay understandable for whoever has to maintain them later?

My work and studies center mostly on distributed systems, software architecture, security and AI engineering. I don't see these as just sets of technologies, but as different ways of dealing with change, risk, complexity and responsibility.

## writing

I write to organize my thinking, record what I learn, and publicly revise what I think.

Here you'll find essays, notes and logs on architecture, distributed systems, reliability, security, artificial intelligence, developer tooling, and technical work beyond code.

These posts come from real experience, real study and real questions. I don't write to hand out universal recipes or definitive answers. Context matters, every decision has costs, and a solution that fits today might stop making sense tomorrow.

The writing is mine. Tools may help with research, organization or review, but they don't replace my voice, my reasoning, or my responsibility for what I publish.

## how i think about engineering

Software doesn't end at the first deploy. It stays alive while products change, teams reorganize, dependencies evolve, and old decisions run into new problems.

That's why reliability, security and operability aren't finishing touches added at the end. They're part of how a system is designed, built and maintained.

Architecture, to me, isn't a drawing detached from implementation either. It's the set of decisions that lets software change without completely losing its shape, its intent, and its ability to be understood.

I see artificial intelligence the same way: not as a replacement for engineering thought, but as a tool that can extend our work. Responsibility for decisions, and for their consequences, stays human.

## now

Right now, I'm:

• ·writing about systems that age well and about technical work beyond code
• ·deepening my studies in architecture, system design, security and AI engineering
• ·exploring new ways for people and software agents to collaborate
• ·building tools, experiments and open source projects

This section reflects the current moment. It should change as my work, my studies and my questions change too.

## mergeando

I also run Mergeando, an open community for sharing experience, building in public and turning conversations into projects.

It brings together people from different areas of building technology — engineering, architecture, quality, security, infrastructure, product, design and other disciplines.

Mergeando is also a reminder of something I try to preserve in my own work: systems may be made of software, but they always exist inside relationships between people.

## transparency

The opinions published here are personal. They don't represent my employer, clients, or any organization I have a professional relationship with.

When I write from work experience, I try to preserve confidential information and keep the text focused on patterns, decisions and lessons that can be discussed publicly.

## colophon

This site is my personal space on the web.

It was built to be simple, readable and durable. The visual language combines editorial writing with terminal elements, while violet works as the main color of my identity.

The site is bilingual, in Portuguese and English. Versions may receive their own adaptations to preserve the meaning of each text, rather than working as purely literal translations.

Dark theme came first. The content, though, should keep working regardless of appearance, device, or the technology used to publish it.