Dear reader,
As the saying goes:
Everything changes.
I think you will love this change.
For a long time, The Optimist Engineer has been a weekly conversation in the form of a single-topic essay. We have delved into design patterns, technical pragmatism, architecture debt, and the lights and shadows of leadership.
However, if building systems teaches us anything, it is that rigidity is the first symptom of obsolescence.
To provide more complete value and make this community more participatory, the newsletter is evolving into a renewed structure with four distinct blocks.
The Read-Only Memory (ROM)
We will leave the usual suspects aside to explore readings with a different perspective.
In this section, we will focus on biographies of computer pioneers, forgotten historical whitepapers that remain entirely relevant, and independent blog posts that question the status quo of our industry.
Would you like to suggest some? I hear you! ππ»
The Open Thread Club
Software development does not happen in a sterile environment, and team dynamics rarely follow an algorithm.
In this space, we will address real dilemmas about architecture, technical friction, or leadership situations sent anonymously by you.
Instead of giving theoretical or dogmatic answers, I will respond with honesty: sharing my own past mistakes in similar situations and the lessons I took away when trying to solve them.
You can start participating RIGHT NOW! Click the button below and tell me your story so I can answer in the next issue ππ»
The Rendezvous
A radar of events about software engineering and technical leadership.
The priority here will not be exclusively massive conferences, but giving visibility to smaller, local encounters or emerging initiatives. If you are organizing a conference or know an event worth sharing, the channel is open for you to send it to me and share it with the community.
Do you own an event or summit? Drop me an email! ππ»
The A-Side
The heart of the newsletter remains untouched.
It will continue to be the weekly thematic article where we keep diving into architecture, design principles, and technical culture with the usual analytical and pragmatic approach.
So, whatβs next?
Next Thursday, Sep 10th, you will receive the first issue with this new format together with a poll, which I would love for you to take part in so I can understand your feedback on the new format.
This change does not seek to add noise, but to build a richer, more transparent, and useful space for everyone.
What do you think about this change? leave a comment or drop me an email!
Be safe,
Marcos.


I like the new direction of the newsletter. Looking forward to it. Good luck with that. π