About Me

Hi, I’m SB, a web engineer passionate about building visually stunning and highly functional web applications. I specialize in frontend development and microservice architecture, working 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

Enabling TypeScript Strict Mode in a Legacy React Project—A Gradual Approach

Image
The Project Background Our App was created in 2017. It is a React application written in TypeScript. At the time, TypeScript was gaining popularity, but strict type safety wasn’t a major concern for most teams. Our knowledge of TypeScript was limited, and the primary goal was to use it for basic type annotations rather than enforcing a fully type-safe codebase. As a result, TypeScript’s strict mode was not enabled. This meant that the codebase lacked certain safeguards, such as strict null checks, no implicit any, and more rigorous type inferences. Over time, as the project grew in size and complexity, the lack of strict typing introduced subtle bugs and made refactoring riskier. Fast forward to today, the project has grown significantly. It now consists of approximately 2270 TypeScript files, making it a massive undertaking to migrate to strict mode. However, the benefits of enabling strict mode—better type safety, easier maintena...
Read more