Blog
Notes on engineering
Backend, architecture and what I learn solving problems at work.
October 27, 2026
Tools I discovered this week
A running list I'll keep updating with tools that turn out worth it, whether someone pointed me to them or I found them while working. First entry: Orca.
October 13, 2026
I just wanted my boredom back
How I cut my screen time from almost 4 hours to 1.5 hours a day with Opal, and by using Instagram only on my PC, like back in the MSN days.
October 09, 2026
The essentials I use to get organized and try to stand out
Finances, English, Claude Code, Notion and YouTube Premium: the tools and habits that keep my routine running. And why, in the end, the most important thing is still to think.
October 08, 2026
How to host a personal website for free on Cloudflare (you only pay for the domain)
Step by step on how this site was published: a .dev.br domain from Registro.br, DNS and hosting on Cloudflare, automatic deploy on every push. The only cost is the domain.
October 07, 2026
Application security starts at the infrastructure
Four infrastructure practices (least-privilege, secrets in a vault, HTTPS and subnet tiers) that cut a big chunk of risk before any code even runs.
September 07, 2026
How to design a well-structured and secure API
A straightforward checklist for designing predictable REST APIs and understanding the difference between authentication and authorization.
September 07, 2026
How Laravel works under the hood: Container, Providers, and requests
What actually matters about how Laravel resolves dependencies on its own, without treating it as magic.
September 07, 2026
How to investigate when someone says "it doesn't scale"
Caching, relational databases, and queues: why there's almost always a specific, nameable bottleneck hiding behind the phrase 'this doesn't scale'.
September 07, 2026
Practical notes I keep rereading
A quick guide to Unix permissions, Node.js, agility, and the Git commands I never forget.
September 07, 2026
How to write a good test before the assert
PHPUnit, the AAA pattern, test doubles, and how to report a bug in a way the team can actually act on.