|
|
|
|
|
by empath75
127 days ago
|
|
I think you have it exactly backwards, and that "owning the stack" is going to be important. Yes the harness is important, yes the model is important, but developing the harness and model together is going to pay huge dividends. |
|
This coding agent is minimal, and it completely changed how I used models and Claude's cli now feels like extremely slow bloat.
I'd not be surprised if you're right in that this is companies / management will prefer to "pay for a complete package" approach for a long while, but power-users should not care for the model providers.
I have like 100 lines of code to get me a tmux controls & semaphore_wait extension in the pi harness. That gave me a better orchestration scheme a month ago when I adopted it, than Claude has right now.
As far as I can tell, the more you try to train your model on your harness, the worse they get. Bitter lesson #2932.