I write to understand systems before they fail.
Most of my work and learning has been around building, maintaining, and fixing software systems — and observing how similar patterns show up in work, money, and life.
This site exists to slow down thinking.
Not to chase trends.
Not to offer quick fixes.
But to examine how decisions compound over time, and how small assumptions become expensive mistakes.
What I write about
My writing usually sits at the intersection of:
- Software systems — architecture, design tradeoffs, real-world failures
- Work and leverage — focus, productivity, and how output actually compounds
- Money and incentives — risk, behavior, and why logic alone isn’t enough
- Clear thinking — decision-making, mindfulness, and reducing noise
These are not separate interests.
They are different views of the same underlying systems.
How to read this site
Most pieces here are long-form and opinionated.
They are written:
- after building something
- after breaking something
- or after watching something fail quietly
If you’re looking for tutorials, frameworks, or growth hacks, this site will likely feel slow.
That’s intentional.
Why I keep this public
Writing publicly forces clarity.
If an idea can’t survive being written clearly, it probably isn’t ready to be trusted — in code or in life.
This site is a record of that process.
A small note on expectations
I don’t publish on a schedule.
I publish when there’s something worth saying.
If something here resonates, you’re welcome to read along.
Contact me
I read messages that are thoughtful, specific, and respectful of time.
You can reach out if you have:
– a considered response to something I’ve written
– a serious question related to systems, work, or thinking
– a meaningful collaboration idea
I may not be able to respond to every message, but I do read them.
Email: notes.duduwrites@gmail.com
If your note is short, clear, and thoughtful, it’s always welcome.