Markus Oberlehner

When multiple people are working together on a project, it is important to define some rules to make sure that everything stays tidy and chaos does not arise.

For the most time, when writing unit tests, I favored the it should ... pattern for naming my tests.

In the last week, thoughts about global state management, technical debt, and using a WET first approach for building components sparked my interest...

In the last week, I enjoyed working with Eleventy and Preact very much.

Last week I had two insights: sanitizing data as early as possible can make it much easier to reason about your code.

In one of my earlier articles, I wrote about how to use functional Vue.js components so that they inherit attributes such as classes and styles.

Last week I had two insights: sanitizing data as early as possible can make it much easier to reason about your code.

The last week was, on the one hand, a busy week and, on the other hand, a slow week when it comes to learning new things.

Last week I discovered some things that made me question myself.

The last couple of weeks, David Khourshid seemed to be everywhere.

Although GraphQL is pretty cool and powerful, I also like the simplicity of good old REST API endpoints.

Last week was a slow week when it comes to discovering or learning about new things.

This week I thought a lot about two topics: reducing complexity and structuring your codebase and naming things.

Last week I did go down the rabbit hole reading about TDD best practices and misconceptions.

In this article, we extend the functionality of our very simple demo application from the previous article to display multiple paginated lists for the same content type.

The data model approach builds on the idea that you have a separate Vuex module for every data model of your application (e.g., users, posts, comments).

Many people, including me, are very skeptical about the utility-first approach of Tailwind CSS and other similar CSS frameworks like Tachyons.

Tailwind is a CSS framework that I never used extensively, but I always found it interesting enough to keep it on my radar and occasionally play around with it.

Tailwind CSS is one of the rising stars in the CSS framework world.

In my last article about building accessible popup overlays with Vue.js we used a simple technique to prevent scrolling in the background.

Sometimes we find ourselves in a situation where the content of a particular area of our website or web app is too big to fit inside of our layout.

If we like it or not, modal dialogs and overlays are a recurring pattern on many websites and apps.

Often it seems like we build the same applications again and again.

One of the main concerns I have when building Vuex-based applications is the tight coupling of components with the Vuex store that seems inevitable when using Vuex.

If you are a regular reader of my blog (thanks to all of you), you may have noticed that many of my articles are about decoupling components from their dependencies.

Today we look at how we can design a system for quickly creating generic Vuex modules for typical CRUD content types.

Listening to one of Full Stack Radio's latest episodes, I was very impressed by the expertise of Matt Biilmann, CEO of Netlify.

In the first part of this series we made sure that we can connect to our NXT and send commands via Node.js.

For several years now, my LEGO Mindstorms NXT has been living a life as a decorative item on my desk.

I love the concept of reactive computed properties in Vue.js.

The more I read about React Hooks and the RFC for the Vue.js Composition API, the more I think about the early days of modern frontend frameworks like React and Vue.js...

In my opinion, the best way to inject dependencies is via factory functions that take the dependencies as parameters.

A few weeks ago I started working on a small side project where it is a requirement to authenticate users.

Today, we will follow the W3C guidelines, on how to build a collapsible dropdown, very closely, to create a solid custom form select Vue.js component that works well for both keyboard and screen reader users as well as people who use a mouse or their fing…

Unfortunately, accessibility (a11y) is often treated as an afterthought by many of us developers, including myself.

When building modern, component-based client-side applications, we often tend to forget about the foundations of web development: HTML and CSS.

On my journey to find ways to improve the rendering performance of large scale Vue.js applications, I stumble upon functional components as a possible solution from time to time.

In one of my previous articles, we examined how we can use JSX in Vue.js to export multiple Vue.js components from a single Single File Component (SFC) .vue file.

A long time ago, there was practically no way around the HTML element for creating complex layouts on the web.

The more I use GraphQl, the more I ask myself the following question: How can I avoid GraphQL queries which query a bunch of fields that were once needed but are no longer used because the code has changed and the fields are now obsolete...

Recently, I was wondering how best to decouple the code needed to track certain form submissions (e.g. conversion tracking in Google Analytics or Matomo) from the business logic of the forms...

Just recently, I discovered a rather new feature in Vue.js: Vue.observable.

In this article, we'll take a look at how we can use the Builder Pattern to make it very easy to create many different form components for each content type of a typical CRUD application...

Recently I've seen a great talk by Jacob Schatz about Phenomenal Design Patterns in Vue.

In this article we experiment with implementing the IoC container pattern in Vue.js.

Because of a recent bug hunting session where it took me a couple of hours to drill down several levels of npm dependencies in order to finally find a try...catch statement with the catch part being empty, I decided to write an article about this topic.

I often wonder how to decouple certain parts of an application best.

In this article, we explore how we can leverage the power of WebSockets to push content and even component updates to simple Vue.js client applications...

Imagine the following scenario: We have a central content distribution server responsible for pushing new content (think of news articles, for example) to a variety of Vue.js-based client applications.

Today we'll explore how we can use Docker to run our tests in a standardized environment in order to prevent false positives because of differences between operating systems...