1. Article

    Me and You, and You and Me, so Happy Together

    Reading time: 5 minutes • Posted 16 days ago
    Hand in hand with Robot

    There's a pattern that keeps showing up in software engineering: the tools that give us the most leverage also demand the most structure.

    Version control unlocked collaboration at scale, but only after teams agreed on branching strategies. Linting and formatting took out a lot of opinions during code reviews, but first we needed to have settled the "tabs vs. spaces" debate. CI/CD pipelines sped everything up, but only once contributors agreed upon a definition of done. AI coding tools are following the same arc, and the teams getting the most out of them have already figured this out.

  2. Tutorial

    Installing Goose-CLI with Ollama for Local AI Coding

    Posted 2 months ago

    If you're (like me) liking the idea of having an AI coding assistant that runs completely locally on your machine (privacy!), there's a good chance you've stumbled upon Goose-CLI. Combine it with Ollama for running AI models locally, and you've got yourself a pretty powerful setup that doesn't send your code to the cloud.

    Let's see what we need to do in order to get both systems up and running, configure them to work together, and set up some convenient shortcuts to switch between coding and writing tasks.

  3. Article

    Upgrading Nuxt v3 to v4 under 30 minutes

    Reading time: 6 minutes • Posted 6 months ago
    Astronauts

    TL;DR: I upgraded a 32k LOC Nuxt app from v3 to v4 in 29 minutes of actual work. Here's how it went and what I learned.

    I'm maintaining a reasonably sized Nuxt application - not massive, but substantial enough to make upgrade decisions matter. We're talking about a project (excluded tests here) with 32k lines of code spread across 173 files, with a healthy mix of 72 Vue components and 44 TypeScript files. The dependency footprint includes 34 production dependencies plus 7 development ones. So, not that big, which makes it a perfect candidate for an upgrade scenario!

  4. Article

    In-Source Tests with Vitest

    Reading time: 5 minutes • Posted 2 years ago
    Four different flasks

    Vue adopted a Single File Component philosophy, which has some benefits over splitting concerns, which you can read up on in the official Vue Docs. From a SFC philosophy, you’d want everything that relates to your component in a Single File. So let’s explore this take with our component tests as well, because why would your tests be any different than your scripts, template or styles?

    We’re going to leverage a feature that Vitest offers, out of the box, to a Vue example code base. Bear in mind that this approach would be applicable to other implementations that leverage Vitest just as easy. Also, this is a thought experiment.

  5. Tutorial

    Combining ReactJS and VueJS in one website using Astro 🚀

    Posted 3 years ago

    With the second major version already released, there's a buzz surrounding Astro and it's hyper performant content focussed web applications. Apart from the focus on speed, Astro is also labeled itself as a "all-in-one" web framework.

    All-in-one meaning that it supports most modern frontend frameworks with zero configuration. I decided to research that claim and I am pleasantly surprised!

  6. Article

    Mandatory article on AI, not entirely written by an AI

    Reading time: 5 minutes • Posted 3 years ago
    Automation

    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.

  7. Article

    Honey, where are my tests?

    Reading time: 6 minutes • Posted 3 years ago
    Where are my pants?

    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!

  8. Article

    Different types of testing

    Reading time: 7 minutes • Posted 3 years ago
    Four different flasks

    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!

  9. Article

    What to choose: Cypress or Playwright 🎭?

    Reading time: 4 minutes • Posted 3 years ago
    Assortment of masks

    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.