HNHacker News
TopNewBestAskShowJobs

cortical_iv

8 karma · joined March 11, 2025

submissionscomments
cortical_iv··on Collective Intelligence: The Next Frontier of AI
This is a very cool nontrivial problem. I worked on this some in a mixture of agent type context. There were lots of failure modes mostly involving model aggregators not working well because they tend to end up plagiarizing what they consider the "best" LLM in the target pool (that is, they don't actually give a balanced view of the target results, but more a winner take all). I had to build all sorts of tooling to avoid this to "anonymize" the content from the LLM target models.

And I only went up to 7 LLM models in my swarm. It seems this has way more, so the issues will only be exacerbated (it isn't clear how much improvement you get once you go beyond, say 10, LLMs in a swarm).

I'm curious what mechanisms are being used for aggregating results returned from LLMs. These are really difficult problems.

I play around with OpenRouter Fusion some, and it does a pretty good job: https://openrouter.ai/docs/guides/routing/routers/fusion-rou...

One nice thing with that application is each LLM is mildly agentic, as it has access to the web.

cortical_iv··on Vibe code is legacy code
I didn't get out of the post a focus on definitions as the main point. I got out of the post a concern about massive technical debt, which is the hallmark of both legacy code and vibe coding. And no, I'm not offering a definition.
cortical_iv··on Vibe code is legacy code
I wouldn't get too persnickety about definitions. There are lots of arguments about what 'legacy' code means. you are throwing around the term quite a bit without really giving any definition at all. 'Code that nobody understands' is fine as a quick and dirty pointer.

Martin Feathers, in the most popular book on legacy code, defines it as code without tests. This is not a good definition at all, but it shows just how hard it is to define it. This is not meant as an attack on anyone: I just think some flexibility and slack is called for here.

You could easily write an long white paper trying to define 'legacy code', and it would be a lot less interesting than the target article here.

cortical_iv··on Lost Chapter of Automate the Boring Stuff: Audio, Video, and Webcams in Python
Makes sense: OpenCV is amazing, but has many rabbit holes and pitfalls. Thanks for posting the draft for us to peruse!
cortical_iv··on Lost Chapter of Automate the Boring Stuff: Audio, Video, and Webcams in Python
I'm curious why you didn't end up including this material?