Over the years of working as a developer and managing software teams, I began to notice an uncomfortable pattern. The methodologies we were using, no matter how popular, didn’t always fit. They came with the promise of solving all problems, but in practice, there were gaps. I felt like many of these methods were created in a different context than what we face today, by people who didn’t always fully understand the real pain points of a modern developer.

The pressure to deliver quickly, the fragmented communication, the friction between teams that often seemed to speak different languages… All of this led me to reflect: are we following methods that truly work for today’s landscape?

And honestly, the answer was: not always.

That’s when the idea for CORE came to me. Not because I wanted to create “just another” framework, but because I needed something that made sense. Something that embraced clarity, ownership of work, resilience in the face of challenges, and, above all, continuous evolution. CORE isn’t a finished product, it’s not a magic solution. It’s a journey, just like any software.

I’m not the kind of person who settles for the status quo. When something doesn’t work, I feel a need to change, to adjust. And it’s this drive for evolution, to improve the environment for developers like me and the teams I work with, that sparked CORE.

If you’ve ever gone through the same kind of frustration I have — seeing projects get bogged down by rigid processes or struggling with a lack of empathy in daily interactions — then maybe you feel this need for something different too.

CORE is my attempt to bring a little more humanity and fluidity into software development. And what do I want most from it? For people, like myself, to feel empowered to question, to suggest changes, and, most importantly, to keep evolving.

Thank you for being part of this journey. I hope, in some way, it inspires yours as well.

Best regards,
Guilherme