Mazin Esam
Software engineer building practical products.
I build web apps and developer-focused products. This site is a brief about me, what I build, and what I write.
About
Hi, I’m Mazin, a frontend developer and software engineer who’s passionate about crafting digital experiences that are as functional as they are beautiful. Whether it’s designing sleek websites or building robust web applications, I love turning ideas into reality with clean code and creative solutions.
When I’m not at my desk, you’ll find me exploring new technologies, diving into a good book, or enjoying a coffee-fueled brainstorming session. I believe great work comes from curiosity, focus, and a genuine passion for what you do and that’s exactly what I bring to every project.
Apps I Made
Latest Blog Posts
View allMentoring for Scale: How Senior Engineers Multiply Team Velocity
9/19/2025
This post details the transition from a highly productive individual contributor (IC) to a multiplier who raises the overall capability of the team. It provides actionable strategies for effective code review, constructive pair programming, creating excellent documentation, and delegational techniques to accelerate the growth of mid-level and junior developers.
Modern State Management: Beyond Redux—A Deep Dive into Architecture
9/12/2025
Moving past introductory state management tutorials, this post will explore the architectural implications of modern, flexible state solutions (e.g., Zustand, Jotai, Recoil, or React Server Components' implicit state). It analyzes how different state patterns affect application scaling, performance, and developer experience in large, complex applications, offering best practices for structuring a global state layer.
The Art of the Rewrite: When to Refactor, When to Rebuild, and Why
9/5/2025
A senior-level perspective on a common engineering challenge. This post will explore the metrics and decision-making framework used to determine if a codebase needs a strategic refactor or a complete, phased rebuild. It will focus on managing technical debt, maintaining feature velocity, and presenting the business case for both scenarios to non-technical stakeholders.