As the great fictional professor Hubert J. Farnsworth said: "Good news everyone!". I'm going to be an author! After a short process of creating an outline and some back and forth between a publisher, I've been given the green light on writing a book on VueJS projects.

This is something I've never done before. The most writing experience I have so far is writing on my personal website, posting articles on Medium and Dev.to and one publication, which was my sole experience working with an editor.

Astro is the new cool kid in town, promising super fast websites with minimum page load. That sounds interesting and Astro has some out of the box improvements that look really promising. So let's discover what the Buzz (all astro related puns are intended) is all about! 👨🏻‍🚀

Astro is a modern, fast, and lightweight meta framework for building web applications. It is built on top of popular web technologies like React, Vue, and Svelte, and provides a simple, intuitive way to build high-performance web applications.

With ChatGPT taking flight with providing an accessible means of interacting with AI models, the debate on the usefulness of AI generated content is all the craze. AI and generated content isn't new, but the ChatGPT marketing campaign and accessibility have opened possibilities to the masses.

With the purchase by Microsoft, (next to its existing Github Copilot service) the future for AI embedded in our tasks is solidified.

Having identified a number of different types of tests, you can already imagine that each tests has its own place in the process.

The process here is key: because software development is complex and consists of several steps, it just makes sense to validate each of these steps. We'll outline a lineair process, but of course in practice there's more iteration between steps. That's fine and is in fact where tests offer the confidence of moving back and forth!

Software development is complex. It involves people talking about an idea or concept and then translating it to code. The code then is compiled, packages or run and we expect a certain result. In all of these (generic) steps, there's room for complexity, interpretation and errors to sneak into the software.

Luckily, testing software has matured and expanded to a level where we can confidently release code that doesn't break on build, only changes where change is needed and the features can even be asserted before writing a single line of code!

When the year closes, it's always a good moment to reflect on the past years achievements to see the bigger picture. If I look back to my achievements, I am proud and grateful for all I've achieved with support of people around me.

A lot of things that have been in the works seemed to click this year and directed my career into a new path, more focussed on engaging people over code. Something that suits me at this point in my career.

I saw this post, by Erik Flowers while scrolling the LinkedIn feed which resonated with some thoughts that have been floating in my mind without anything to latch on to. But now those thought found something to root.

I am currently working as a "software engineer" (commonly also referred to as "frontend developer") and although I like to label myself more as an "interaction developer" my main domain consists of designing software architectures and writing code. My background has always involved some level of getting involved with the user experience (UX) aspect. And while that may seem something that sticks out, I feel it is both to build good software and unfortunately also something that is not commonplace.

I was seeing a lot of Playwright mentions in my timelines recently, so I decided to investigate what the fuss was all about. Playwright, as it turns out, is a tool for executing end to end (e2e) tests, similar to Cypress.

With Cypress being my go to tool to integrate e2e tests, I figured I could do a comparison on the two, to see which better fits my needs at this point.