Markus Oberlehner

Reviewing code has become dramatically more expensive relative to the cost of writing code.

Is it worth automating things?

There are plenty of good reasons to turn your back on the major US technology companies: from shady monopolistic business practices (e.g., app stores); to crafting ever more addictive algorithms that tie us to our screens; to enabling state mass surveilla…

Visual regression testing is the perfect tool to catch regressions within our UI component libraries and applications early, yet few teams practice it.

Stop sharing only the things that went well!

What do we mean when we talk about "magic" in programming?

Imagine you train a toddler to read, mixing in texts about physics and mathematics.

'Naming things is hard!'

Specmatic quickly became my favorite tool for contract testing microservices and for using it as a stub service to test frontend applications.

After being rejected to speak at several conferences, I wondered: Why is it so important to me?

I'm currently working on building a comprehensive form component with React.

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.

Storybook’s visual regression testing tool Chromatic is powerful but expensive.

Nowadays, there are plenty of ways to run and deploy our Next.js application to the World Wide Web.

Although microservices and microfrontends have been popular choices for building modern software systems, many projects fail to reap their promised benefits.

Recently, I was back on the job hunt.

Vite brought super fast bundling and hot reloading to our regular dev workflow, and Vitest is doing the same for our testing workflow.

In this article, we'll explore the integration of AI-assisted development with established best practices.

I could never quite wrap my head around how to test SSR applications (Nuxt, Next.js, Laravel, etc.) that talk to HTTP APIs (e.g., microservices).

In this article, we’ll explore using SQLite with the VSS plugin to build a “similar products” functionality with Nuxt, Vectory Search, and SQLite...

One thing that is often overlooked in the current AI chatbot hype is another use case for Large Language Models (LLMs): Vector Search with text embeddings...

This article might not meet your expectations if you're looking for a black-and-white answer to whether returning composables from other composables in Vue is an anti-pattern.

Managing data across different components is a common challenge when working with modern web frameworks.

When we dive into the world of testing in programming, it's easy to get caught up in the numbers game—how many tests have we written?

When it comes to coding, sometimes less is more.

LLaMA 2, a fresh Open Source language model by meta, is a powerful tool for natural language processing tasks.

In this article, we'll dive into the world of Nuxt 3 and Docker, exploring how they can work together to streamline our development and deployment processes.

We often find ourselves needing to use various command-line interface (CLI) tools written in different programming languages.

In this article, we will discuss the problems associated with attribute inheritance, also known as fallthrough attributes, in Vue components and why it might be best to avoid using them.

In the ever-evolving landscape of web development, we have seen a shift from traditional Multi-Page Applications (MPAs) to modern Single Page Applications (SPAs), each with advantages and drawbacks.

ChatGPT has recently gained significant attention due to its powerful natural language understanding and generation capabilities.

Error handling is essential when developing web applications to let users know why and what is going wrong and ensure a smooth user experience.

ChatGPT has recently gained significant attention due to its powerful natural language understanding and generation capabilities.

Dive into the world of TypeScript's powerful utilities, Omit and Partial, as we explore their potential in data creation and updates.

Are you seeking a trusty sidekick to help you tackle your writing projects?

Creating custom component libraries for multiple products or applications can be challenging, particularly for companies that need to maintain two or more different design systems.

Did you ever encounter the problem that the space between a text block and some other element does not seem right?

The JavaScript ecosystem has a lot to offer when it comes to testing.

Now and then, fierce debates ignite on Twitter about whether the term Software Architecture is misleading or even harmful.

Every couple of months, I reach a point where I have to declare TODO bankruptcy.

When we first start to dip our toes into the deep waters of automated software testing, all those different kinds of tests can feel intimidating.

Ideally, Vue components are self-contained pieces of UI without any observable side effects to matters outside the component's scope.

A tweet by Manuel Matuzović reminded me that in Vue 3, we finally have fragments.

When starting a new project or refactoring an existing one, the question often arises: how to set up the project's directory structure.

The Composition API makes it very easy to share code between components in our codebase or even across projects via npm packages.

Over the past few weeks, I've been thinking a lot about effectively maintaining shared code within an organization.

What makes the Vue 3 Composition API so much better than the Options API is code sharing.

Whenever we find a severe bug that is caused by an error in a complicated piece of code, in my experience, the first instinct is that better documentation is needed.

Out of the box, Cypress offers an amazing live-reloading feature.

When testing components (e.g., Vue or React) or regular JavaScript modules, we typically want to decouple our test code from the implementation as much as possible.