This post was written using AI as an experiment to take my most recent LinkedIn posts and to expand them in a post while adding supporting citations and using the voice I've established in my blog.

I'm impressed. It maintains my voice fairly well and definitely expands on what the points I made in my LinkedIn posts. A couple of things are clunky but nothing is truly terrible, even though the annoying AI "chronologic narrative" cadence is prevalent...

A friend sent me an article by Dhruval Makwana titled Flow-First Coding: Why Your Best Code Happens When You Stop Trying So Hard (now deleted), since there's some overlap in my personal coding philosophies.

The piece points in the right direction but it misses the critical point about its core ideas.

When things are wrong in programming it's obvious....

It only took me a year but I finally figured out how to type a Vue Input component.

Unlike React, Vue doesn't ship with synthetic types for inputs which can cause problems for Typescript.

I turned to everyone's favorite "AI" programmer, Claude, and politely asked for the solution:

<script setup lang="ts">
function ...

With these new tools, the adjustment was simple.

My folder structure is updated to this:

/src
  /pages
    +Layout.vue
    /index
      +Page.vue
    /articles
      +Page.vue
      /articles/@articleSlug #dynamic route
        +data.js
        +Head.vue
        +onBeforePrerenderStart.js
        +Page.vue
        +route.js
        +title.js

Two item's I didn't include above are +onBeforePrerenderStart.js and +route.js.

These...

GraphQL seemed like such a great idea when I first learned about it

Essentially it's the reinvention of an API endpoint. Instead of hitting a specific API to get back a certain set of data, let's have one endpoint that will return what's requested.

For example instead of an endpoint to retrieve a user's data, typically /user, instead pointing to /graphql and making requests against that endpoint for what a developer would like...