if you're building an agent or a harness, you need to be an order of magnitude closer to the code than you would be normally
models are VERY bad at building harnesses & agents - not sure if it's lack of training data or smth else
but they have exceptionally bad intuitions about context management and the agent loop and caching and a lot of other components that matter a LOT
it is very high-leverage to design the code yourself - if not typing it by hand, still do the program design yourself
@NathanFlurry Iβm somewhat confused about the βflavourβ of isolate here and the one on CF. https://t.co/e1OliipIeL claims it would run CPython, does this mean it can run cpython inside the isolate?
So far I've only used Rust with Astra, but so far this code is like the sloppiest slop i've ever seen. It all works well and the abstractions are pretty damn good, but holy shit this code looks rancid.
@alexanderrX_ At the end of the day it's going to boil down to value provided per unit spent, it's much more obvious in tech right now, but probably the patterns in finance haven't been as well known yet
Most of these AI models are trained to do great on coding tasks which are easy to test, the same cannot be said for a lot of finance related tasks, there's no feedback loop to say that the model is doing a good job.
Some folks in investing we showed it to either refused to admit it did a decent job for a draft from one shot but also realise that the wall of text probably needs someone sitting down to ensure it followed proper rigour and all numbers are cited, so they are jaded.
We are trying to improve and change this at @itoflowai
@ashleypeacock A brand new DO; a concrete use case, I was researching something in an agent and it brought up an alternative research path. I want to follow both of them, or fork it into a new one to hand it off to a colleague
AI has eaten tactical programming, so juniors need strategic experience in a low-blast-radius environment.
Here's one way to make that happen:
1. Give them responsibility over a large chunk of work
2. That work must be low stakes, but not no stakes - ideally an internal tool (AI makes these kinds of projects easy to justify)
3. Let them move fast and fail fast. Give them the same AI budgets as your senior engineers.
4. When failures happen, work with them to figure out what went wrong (learnings can also be pulled upwards into the rest of the org)
In a sentence:
Hire juniors. Give them work that matters. Watch them fail. Pick them up.