184 karma · joined September 26, 2022
https://convergence-frontier.com
I've since discontinued hosting it, but happy to add you all and merge into an official PG offering: https://www.reddit.com/r/SideProject/s/VtYKxjrMme
Keep up the good work!
Not difficult at all.
Similar idea, but much simpler and focused!
ELI is built as an on-ramp for those that don't have the education al background to get over the learning curve required for this method to be practical.
MCP are tools - might as well have just called it API for AI, but that ship has sailed.
It's 100% apples and oranges!
The post provides a lot of good food for thought based on experience which is exactly what the title conveys
The idea of assigning a code-owner agent per directory is really interesting. A2A (read: message passing and self-updating AGENTS.md files) might really shine there in some way.
They can do so at an accelerated rate using AI on verifiable subject matter. Use something like SRS + copilot + nano (related: https://srs.voxos.ai) to really internalize concepts.
Go deep on a project while using AI. To what extreme can they take a program before AI can't offer a working solution? Professors should explore and guide their students to this boundary.
Obligatory reference to "The illustrated guide to a Ph.D." - https://matt.might.net/articles/phd-school-in-pictures/
While the layoffs data is starting to look scary, corporate policy and regulation will very likely lead to an explosion of HIL jobs.
Andrej Karpathy (https://x.com/karpathy) released (and then removed?) a cursory analysis on ~300 occupations, but JTI tracks over 600 across BLS and O*NET data.
One of the things that's becoming clear is that job security will map to lack of verifiability in a given subject matter. That's somewhat concerning.
I figured that an LLM (Claude Opus 4.6) could extend the concept to apply to a number of mathemtics topics and it did!
There's an aspect to this which I feel could really help people who are not mathematically inclined to really internalize core conepts to the point that actual math makes more sense to them.
Appreciate any feedback I can get on it!
Why would I want it to "think" more than it apparently needs to with 4.5.
The posted link is a research report on the topic - in full disclosure generated by a custom research agent I've been working on.
I'm sure that others are working on other novel UXs for fast decision making to coordinate their agents. I'd love to hear any insights you've gained so far.
My hunch is that we'll see a number of workflows that will benefit from this type of distributed system. Namely, ones that involve agents having to collaborate across timezones and interact with humans from different departments at large organizations.
That's great to hear. It makes sense given the MCP server in this case is mainly just a proxy for API calls. One thing I wonder is at what point do you decide your single tool description packs in too much context? Do you introduce a tool for each category of subcommands?
The error amplification numbers are wild! 17x for independent agents vs 4x with some central coordination. Clink provides users (and more importantly their agents) the primitives to choose their own pattern.
The most relevant features are...
- work queues with claim/release for parallelizable tasks - checkpoint dependencies when things need to be sequential - consensus voting as a gate before anything critical happens
The part about tool count increasing coordination overhead is interesting too. I've been considering exposing just a single tool to address this, but I wonder how this plays out as people start stacking more MCP servers together. It feels like we're all still learning what works here. The docs are at https://docs.clink.voxos.ai if anyone wants to poke around!
It's also important to gather consensus among the team and understand if/why work hour estimates differ between individuals on the same body of work or tasks. I'd go so far as to say that a majority of project planning, scoping, and derisking can be figured out during an honest discussion about work hour estimates.
Story points are too open to interpretation and have no meaningful grounding besides the latent work hours that need to go into them.