Designing systems, analyzing solutions, sharing vision

by

Welcome to my digital headquarters. As a Software Architect, my professional life is defined by technical decision-making and the analysis of complex structures. This site serves as the central hub for my broader reflections on the software industry, professional insights, and deep dives into the books I study.

My Ecosystem of Projects

To maintain focus and depth, I have organized my technical contributions into two specialized platforms:

  • NotDefine.dev — Low-Level Programming My current primary focus. Here, I publish in-depth analysis and tutorials on Go and Rust, exploring performance, memory safety, and high-efficiency systems.
  • SwiftUI.blog — Apple Ecosystem A dedicated space for modern declarative development with SwiftUI. This site also supports my academic activities and lectures for university students.

Reading List & Reviews

I firmly believe that a Software Architect’s growth is fueled by methodical study. In the Books section of this site, I share my personal reviews and summaries of technical texts and essays that I consider essential for evolving in this field.

This blog is where you will find the “behind the scenes” of my vision: reflections that are perhaps less structured than a code tutorial, but necessary to understand where the world of software development is headed.

Exergonic or Endergonic

by

Do you remember the difference between an exergonic and an endergonic reaction? Honestly, I came across these terms again after many years while reading the book How to Take Smart Notes.

To be concise, I read this passage:

“You may remember from school the difference between an exergonic and an endergonic reaction. In the first case, you constantly need to add energy to keep the process going. In the second case, the reaction, once triggered, continues by itself and even releases energy. The dynamics of work are not so different. Sometimes we feel like our work is draining our energy and we can only move forward if we put more and more energy into it. But sometimes it is the opposite. Once we get into the workflow, it is as if the work itself gains momentum, pulling us along and sometimes even energizing us. This is the kind of dynamic we are looking for.”

So there are activities that drain our energy and others that recharge it.

Although the main purpose of the book is different, this passage made me reflect on the activities we do with AI. Are they exergonic or endergonic?

I’m starting to think that activities done with the help of AI can actually drain our energy. As I read online, I see people trying to produce more and more, sometimes risking burnout. It doesn’t always feel like being in a state of flow, where producing more also recharges us.

Is AI helping us enter a state of flow, or is it replacing it with compulsive productivity? What do you think?

Journaling and time management in the 2026

by

This post is an update of a post that I wrote at the end of 2023. I’d like to share my experience with journaling and time management. I started eight years ago to improve my time management skills and stay focused. I’m not selling anything and don’t have a magic formula, but I hope my experience can help someone. As you may know, my interest lies in computer science; I always have some side projects that help me learn something new, I also enjoy reading (on very different topics), and I’ve just started taking guitar lessons. Last but not least, I’m a husband and a father of three. At the end of the post, you’ll find a bibliography of the books that inspired me (as usual, NO referral links. When I want money from you, I’ll ask directly 😄).

Read more

Do you also think the past of open source was made of spotless heroes?

by

Do you also think the past of open source was made of spotless heroes?

Last Saturday, I had the pleasure of speaking at my city’s Linux Day with a short talk titled “Rust in the Linux Kernel.” The presentation sparked interesting discussions: younger attendees approached me during the break to dive deeper into technical details, while some of the more experienced ones raised ideological questions.

I noticed that even today, some people are still bothered by open source projects sponsored or supported by companies—as if that made them somehow impure. But the truth is, the idealized past many people long for never really existed.

Take the C language, for example—it was born in AT&T’s labs, not in the basement of some flawless hero. And the Linux kernel itself didn’t emerge to overthrow any kind of power, but from a purely technical dispute.

Maybe if we stopped idealizing and distorting reality, we’d have more time (and clarity) to build even higher-quality technology.