131 karma · joined June 16, 2017
Your subscription is not subsidised, it is just closer to the actual cost of the model…
Like if I’m an SRE/DBA and you running massive update queries in a single transaction, that is the first thing I’m getting rid of.
You mean the industrial scale distillation attack you perform on the entire corpus of human knowledge… idk, call me cynical but you reap what you sow.
It should be treated as an explicit artefact of the codebase for Humans and Agents to work with.
To me the interesting part of the harness is what you add on top, Brigitte Böckeler calls it the outer harness. I prefer the term Your Harness, your harness breaks down into two things: Skills and Loops.
Skills change what the agent knows and the loop changes how it works and checks itself. Both can mostly be encoded in Agent Skills
Your Harness should mostly agnostic to the agent you use.
I use the humanize skill to clean up AI written work before handing it over to colleagues.
building something people love can make you a billionaire, but most billionaires did not build something people love, and most people who’ve built something people love are not billionaires.
So complaining about having to contribute to the society that gave the conditions for your vast wealth is going to get you 0 sympathy
https://shopify.engineering/shopify-monolith http://sporto.github.com/blog/2012/11/15/a-pattern-for-servi...
So unless you’re into burning tokens having AI generate untested libraries, I’d stick to using the most idiomatic tool for the problem you are tackling.
Cool story, but what runs when?
For most cases you will still be comfortably in the JVM/golang performance window.
Rust is great language, fighting the borrow checker sucks, don’t do it if you don’t need to.