About Me

Hi, I’m SB, a web engineer based in Washington D.C., passionate about building visually stunning and highly functional web applications. I specialize in frontend development, microservice architecture, and cloud infrastructure, holding an AWS Solutions Architect certification. I work with technologies like React, GraphQL, and Node.js to create seamless digital experiences.

Currently, I work at a Swiss media company, where I help develop and maintain scalable web solutions. My background in mechanical engineering, which I studied in Lucerne, has given me strong analytical skills that I apply to problem-solving in software development.

Why This Blog?

I started this blog to share my experiences, insights, and lessons learned from working on modern web applications. Whether it’s tackling complex migrations, optimizing frontend performance, or exploring new technologies, I want to document my journey and contribute to the developer community.

What You’ll Find Here

  • Technical deep dives into React, GraphQL, and backend architecture
  • Real-world problem-solving from my projects
  • Tips and best practices for writing maintainable and scalable code
  • Personal experiences as a web developer navigating the ever-evolving tech landscape

I’m always looking to learn, collaborate, and exchange ideas with like-minded developers. If any of my posts resonate with you, feel free to reach out!

Let’s build better web experiences together. 

Comments

Post a Comment

Popular posts from this blog

My 4-Step Study Plan for Passing the AWS Solutions Architect – Associate

As a Web Engineer focused on full-stack implementations, I've spent years immersed in the AWS ecosystem. My daily toolkit prominently features services like EC2, DynamoDB, Redis, Lambda, API Gateway, and S3. While I was comfortable building and deploying applications, I knew there was a vast universe of AWS services and architectural best practices beyond my day-to-day work. This year, I set a personal goal at work to achieve the AWS Certified Solutions Architect – Associate certification. It wasn't just about a badge; it was about truly going deeper into subjects I touched lightly, understanding how to architect robust solutions, and ultimately becoming a more well-rounded cloud professional. I'm thrilled to say I passed the SAA-C03 exam on my first attempt with an impressive score of 903/1000! Here’s the exact study plan I followed over nine consistent months. Introduction: What is the Solutions Architect - Associate Exam? The AWS Certified Solutions Architect – Associate...
Read more

Introducing a Baby Chaos Monkey for Our Microservices

In complex systems built on a microservice architecture, resilience isn’t just a nice-to-have, it’s essential. One common approach to testing system robustness is Chaos Engineering, where you intentionally introduce failures to see how well your system recovers. Netflix’s Chaos Monkey is a famous example: it randomly kills services in production to ensure systems can handle failure gracefully. While that level of chaos might be overkill for most teams (especially outside of production), the core idea, testing your system’s response to failure, is invaluable. Inspired by this, we recently added a small but effective piece of middleware to one of our services: a manually triggered route-level failure tool that acts like a “baby Chaos Monkey.” Our infrastructure is composed of many interdependent microservices. Even small changes can have surprising ripple effects, especially when services rely on each other in subtle ways. This middleware gives us a lightweight, controlled way to simul...
Read more

Modern API Development with TypeSpec and OpenAPI

Designing robust and well-documented web APIs is a crucial part of modern software development. One of the most widely adopted standards for describing RESTful APIs is OpenAPI. It provides a machine-readable format—typically written in JSON or YAML—that defines the structure, endpoints, request/response formats, and other aspects of an API. This schema becomes a single source of truth, powering everything from interactive documentation to client libraries and server stubs. However, writing and maintaining OpenAPI specifications by hand can quickly become a chore. The syntax is verbose, and small mistakes in the structure can lead to frustrating bugs or inconsistencies across different parts of the system. This is where TypeSpec comes in. TypeSpec is a language developed by Microsoft for describing APIs in a more developer-friendly way. Instead of wrestling with raw OpenAPI YAML, you write a TypeSpec file that feels more like TypeScript: concise, expressive, and modular. From this s...
Read more