Comment by graemefawcett

Sorry, I had to get my kids off to school (there's two of them) and daddy tends to need some help on the best of days, but the abstraction is already designed for a polyglot runtime and my entire current platform is based on Ruby (she's just so pretty isn't she...) so the guts were there. I had a Ruby SDK for the graph from a week or two ago laying around so I just needed to get the fence processor and context injection wired up.

This I think proves the power of what Obie is saying. We do RSpec now and it's glorious

https://tech.lgbt/@graeme/115622344011576598

That shows how we can create a single node on the graph with a pair of {{include:statements}} and a bit of ${interpolation:based-pointer.math} and poke and peek tools in an MCP proxy turns a markdown file into an Rspec test runner, just by reading the file. And that same {{include:}} lets me drop that pattern anywhere I want all over the graph, which is pretty neat.

Obie's definitely on to something with this. There's a rather lot of negative emotion surrounding the changes to our profession. There's a certain lack of joy bleeding through many of the comments. Computing doesn't have to be that way, didn't used to be anyways. If you're smart about your verification process, if you're smart about optimizing the framing of your intent, this isn't a scary world we're all crashing headlong into. Remember what they're for - they're generative not thinking - and they'll serve you well.

Or not

They can be little gooses sometimes ;)