I am passionate about solving complex problems and turning ideas into practical, efficient solutions. I enjoy taking on new challenges that encourage me to learn, grow, and continuously improve both my technical and professional skills.
I believe that continuous learning is essential in technology, which is why I constantly seek opportunities to expand my knowledge and stay up to date with new tools and best practices. I am driven by projects that create real value, solve meaningful problems, and make a positive impact on people and organizations.
With a mindset of curiosity, resilience, and collaboration, I strive to deliver high-quality solutions while continuously growing as both an engineer and a professional.
I'm a software engineer passionate about building products that solve real-world problems. I enjoy designing clean, scalable solutions and continuously learning new technologies to improve both my technical skills and the products I create.
I value curiosity, simplicity, and continuous improvement. Whether working independently or as part of a team, I strive to build software that delivers meaningful impact and provides an excellent user experience.
I'm active on GitHub and on LinkedIn. I write about what I'm building on the blog.
I enjoy learning about fun technical challenges and collaborating with great teams. Reach out if you want to find a way to work together!
Blog
Notes on keeping a build fast
Jul 14, 2026 · 6 min read
This is a sample post laid out the way every article on the site will be. Replace the words; the structure below shows how each element is styled, so you can see headings, lists, quotes, code, and images before writing anything real.
The measure stays at the same 800px column as the rest of the site, which keeps line length comfortable for long reading. Body copy runs at 16px with slightly looser leading than the homepage.
A section heading
Sections break the piece into a few clear moves. Two or three per post is usually enough; more than that and the article probably wants to be split in two.
Bulleted lists sit at the same rhythm as paragraphs.
Keep each item to a single idea.
Three to five items reads best.
A pull quote for the line worth remembering. It stays quiet, set off by a rule rather than a box.
A smaller subheading
Inline code such as npm run build sits inside a sentence without breaking the line height. Longer snippets get their own block:
const cache = new Map();
function memo(fn) {
return (key) => cache.get(key) ?? cache.set(key, fn(key)).get(key);
}
Image placeholder — drop a screenshot or diagram here
Captions run small and grey, centred under the image.
Close on a short paragraph that lands the point, and link outward where it helps: the repository for anyone who wants the code.
