Who is Essyefe?
· 5 min
My name is Samuel F., and this is the first post on this blog, before getting into p99s, caching, or database indexes, it's worth explaining who's writing and why.
Full cycle, in practice
I work as a full cycle developer: I don't stay in just one layer of a system. I go through design, implementation, deployment, observability, and the maintenance that comes after, because, in my experience, that's exactly where performance problems show up: a decision made in one layer (an index, a caching strategy, a schema) tends to turn into a symptom in a completely different layer weeks later, far from where the real cause is.
A different stack on every project
I've worked across a range of technologies on different projects, Python, JavaScript and TypeScript, Java, Go, databases like PostgreSQL, MySQL, and Redis, infrastructure on Docker, Kubernetes, and Linux. What repeats across all of them isn't the language or the framework of the moment, it's always the same question: where's the bottleneck, and what does it actually cost to fix it, not just relieve the symptom.
Why this blog exists
This is where I document what I learn trying to answer that question: real project case studies under "Selected projects", and posts about performance, technical comparisons, and curiosities here on the blog. The idea is simple, record the reasoning behind each decision, not just the final result.
Why "Essyefe"
If the name looked odd: "Essyefe" is "S.F." spelled out, my initials.