A white label platform with several different brands built using Angular, PHP, and C++. I implemented features across the stack, as well as the occasional DevOps task. Due to my primary focus on front-end technology, I took the lead on improving the code quality and test coverage of the front-end stack. One of the major technical problems I solved was to introduce a new build system and a re-architecture, resulting in massive performance and team velocity gains: e.g., where previously re-compilation took up to 5 minutes, my changes diminished this to less than 30 seconds. The main challenges were availability, reliability, and performance, balanced by a continuous focus on improving the UX and UI.

A B2B data-analytics and insights platform developed by TD Reply and used by BMW, Miele, Telefonica, etc. An interesting feature of the product was the fact that it was split into a client facing (React + Redux; Highcharts) part and an admin panel part (Angular). Ruby-on-Rails and MongoDB completed the stack, making it one of the most interesting projects I have worked in from a purely technical perspective. One thing to note here is that, since the front-end code had a test coverage of more than 85% and we were following the TDD paradigm, I spent as much time writing specs in Jasmine and Jest as I did developing in Angular and React. I would also classify this as the project with the strictest code reviews I have ever seen to date – but also the one most closely adhering to current industry best practices in a more general sense.

The new website of the football club, developed by a cross-department Bulpros team in conjunction with Microsoft Germany. Built in AngularJS, bootstrapped in an ASP.NET Razor app, this was a challenging, complex, long-term project with dynamically changing requirements and interesting, unexpected technical problems. As the most experienced Front-end Developer in the project, I worked on implementing a significant percent of the entire front-end stack and was tasked with solving the most complicated issues we encountered, while applying the relevant best practices for a component-based architecture. Despite joining the project months after the initial commit and long after lots of wrong decisions had been made, we managed to deliver to spec. I would also consider it a learning experience, during which mistakes were made by both the management and engineering teams. It helped me understand the value of long-term planning and transparent decision-making, as well as the impact of a good process.

A sports and fitness tracker web app, developed by a cross-department Bulpros team for AOK Nordost. Built in AngularJS and Java (Spring). Initially joining the team as a Junior Front-end Developer, I created or contributed to most components of the web app. As the project progressed, I ended up as the main developer with front-end experience and used this opportunity to hone my skills and progress to the next level in both seniority and knowledge, all the while solving challenging problems and gaining a deeper understanding of JavaScript as a language and eco-system.

The first app that lets you generate a playlist for the book you're currently reading. Initially, I decided to build this as a way to learn a bit more about React Native - I decided to build it for myself. It was challenging to maintain the discipline to adhere to best practices when I was the only developer in the project – and especially considering the fact that no one will ever see the code. However, numerous iterations and 120+ commits later, I think I made the right choice by using git, refactoring as I implemented new features, adding meaningful comments, and trying to write self-documenting code.