Markus Oberlehner

Blog

Read articles about React and Next.js, Nuxt and Vue.js, JavaScript and TypeScript, CSS, Test Driven Development, and Software Architecture.

Non-English Variable, Function, and Symbol Names in Code

Recently, I switched jobs from karriere.at, Austria's largest job platform, to the Austrian Federal Computing Centre, where my colleagues and I work on modernizing Austria's digital tax services. One of the first things I noticed, looking at the new codebase, was that we heavily use German terms for naming certain classes, functions, and variables. At first, this seemed to me like a giant red flag. But now, after seeing the problem through a different lens, I realize that in many instances, it can make a lot of sense to use our native tongue to name certain things...

Running Visual Regression Tests with Storybook and Playwright for Free

Storybook’s visual regression testing tool Chromatic is powerful but expensive. Luckily, with tools like Playwright, we can build a free alternative for running visual regression tests on our UI components. In this article, we’ll explore how to integrate Playwright with Storybook and use Docker to ensure consistent test results across different machines and CI environments.

Running Next.js with Docker

Nowadays, there are plenty of ways to run and deploy our Next.js application to the World Wide Web. Yet, especially in an enterprise environment or when we don't want to depend on a particular provider like Vercel, we may consider bundling our Next.js-powered application within a Docker container...

The Microservices and Microfrontend Mindset: Think Decoupled

Although microservices and microfrontends have been popular choices for building modern software systems, many projects fail to reap their promised benefits. In this article, we explore why this happens and how embracing a decoupled mindset can help you get the most out of these architectures.

Using Testing Library jest-dom with Vitest

Vite brought super fast bundling and hot reloading to our regular dev workflow, and Vitest is doing the same for our testing workflow. So I'm mostly transitioning away from Jest in favor of Vitest. But there are a lot of amazing tools in the Jest ecosystem, and not of them can be easily replaced. Luckily, the Vitest API is mostly compatible with the Jest API...