Lately I've been writing DSLs with the help of these LLM assistants. It is definitely not vibe coding as I'm paying a lot of attention to the overall architectu

Lately I've been writing DSLs with the help of these LLM assistants. It is definitely not vibe coding as I'm paying a lot of attention to the overall architecture. But most importantly my focus is on the expressiveness and usefulness of the DSLs themselves. I am indeed solving problems and I am very engaged but it is a very different focus. "How can the LSP help orient the developer?" "Do we want to encourage a functional-looking pipeline in this context"? "How should the step debugger operate under these conditions"? etc. GET /svg/weather |> jq: weatherData |> jq: ` .hourly as $h | [$h.time, $h.temperature_2m] | transpose | map({time: .[0], temp: .[1]}) ` |> gg({ "type": "svg", "width": 800, "height": 400 }): ` aes(x: time, y: temp) | line() | point() ` I've even started embedding my DSLs inside my other DSLs!