Jason Kuhrt

Thanks to @colelawrence.com I today discovered ampcode.com. Reading their changelog (at /news) and getting excited. There are some great ideas here (I'm excited to read other devs' prompt flows), pace of change appears breakneck, and they're removing paper cut after paper cut that I've ...

... on the fly AI-optimized CLIs, so good); and I keep scrolling, still into only mid October. One thing I'm missing though is no subscription model like Claude Code Max. My expectation is that I will pay much more per month using api billing, at least that's what my current CC stats tell me.

Thanks to @colelawrence.com I today discovered ampcode.com. Reading their changelog (at /news) and getting excited. There are some great ideas here (I'm excited to read other devs' prompt flows), pace of change appears breakneck, and they're removing paper cut after paper cut that I've ...

Cool to see this @grain.social. This year I migrated off of Instagram to my personal website kuhrt.me/capturing. But I do enjoy a healthy social experience. Maybe that's what Grain is/will be/remain as :). I am sceptical that pretty much any social platform of sufficient "success" (scale) will ...

... succumb to entropy against civility and user experience but I want to be wrong, @bsky.app seems to be progressing ok for example (not paying so much attention but that's kind of the point, I pay no attention to/on X but still readily have negative experiences there), but its still early.

On design: Thinking of 'One obvious way' versus 'expressiveness' (e.g. Python versus Ruby), not as a dichotomy but as a continuum, have the expressiveness AND then allow layering on the 'obvious way' for <thing> ([mono]repo, package, file, block, ...). In other words when designing an interface, ...

I would appreciate a TypeScript LSP MCP, Claude Code could turn a laborious non-deterministic process (easily 1+ minutes on large code bases) of identifier renames into a few seconds deterministic process. For now I try to do that for Claude but steals some degree of flow from me.

I’m looking for my next opportunity 👨‍💻, short/long contracts or part/full time. My experience is 15 years across the stack and architecture often focused on open source and next generation developer tooling, libraries, frameworks in the TypeScript space. If your company or project is ...

striving to achieve world class developer experiences (DX) and want help I would love to talk! More generally, If you’re building something ambitious with Effect and/or take quality TypeScript seriously (or want to), I would love to talk too.

I’m looking for my next opportunity 👨‍💻, short/long contracts or part/full time. My experience is 15 years across the stack and architecture often focused on open source and next generation developer tooling, libraries, frameworks in the TypeScript space. If your company or project is ...

striving to achieve world class developer experiences (DX) and want help I would love to talk! More generally, If you’re building something ambitious with Effect and/or take quality TypeScript seriously (or want to), I would love to talk too.

I've been making big strides with Graffle the past couple weeks, such as around the static builder and support for variables, docs, and type level string parser. Accordingly I revamped docs to cover everything one should need to know about these features. Here's a rundown:

I've been making big strides with Graffle the past couple weeks, such as around the static builder and support for variables, docs, and type level string parser. Accordingly I revamped docs to cover everything one should need to know about these features. Here's a rundown:

graffle.js.org/guides/docum... - This documents GQL TS LSP Setup for those using native GQL syntax. Kudos to @kitten.sh et al who made and maintain that! So thanks to that, one gets autocomplete with whichever syntax they use. Meanwhile Graffle string parsing ensures their symmetric type safety to.

I've been making big strides with Graffle the past couple weeks, such as around the static builder and support for variables, docs, and type level string parser. Accordingly I revamped docs to cover everything one should need to know about these features. Here's a rundown:

graffle.js.org/guides/docum... - This covers custom scalars which is a cool GQL feature but typically a PITA to actually realize in practice. Graffle goes the extra miles to make it hum. It is such a particular, perennial and cross cutting topic in GQL that I gave it a page its own too.

I've been making big strides with Graffle the past couple weeks, such as around the static builder and support for variables, docs, and type level string parser. Accordingly I revamped docs to cover everything one should need to know about these features. Here's a rundown:

graffle.js.org/guides/docum... - This covers actually doing something useful with those built documents! It also shows off the fancy ergonomics of how variables and operation names are fully accounted for in a, again, progressive way (e.g. api simplifies when only one operation etc.)

I've been making big strides with Graffle the past couple weeks, such as around the static builder and support for variables, docs, and type level string parser. Accordingly I revamped docs to cover everything one should need to know about these features. Here's a rundown:

graffle.js.org/guides/docum... - This covers the document builder at its base, focusing on its syntax. I use tabs to make it easy to compare to how native GraphQL looks. I'm happy with how well my design has held up to native, often being only mildly more verbose (:true bits are main culprit)

So last month I gave two talks at GraphQL Conf in Amsterdam and it was a lot of fun and challenge for me but unfortunately a glitch means my talk on Polen (polen.js.org) will never see the light of day, though my shorter talk on Graffle (graffle.js.org) will.

I am excited for voidzero.dev/posts/announ... and will begin using it this week on some of my projects (more on that soon). Thanks @vite.dev @vitest.dev etc. and all the peeps involved reaching this point. Every tool in the chain scratches an itch I have.