chapel

Someone using an LLM to code isn't calling themselves a great coder just because the LLM is writing good code. Being a software engineer/developer (whatever you want to call it) is not defined solely on your ability to write code.

To go back to your point, before the F1 driver (LLM) was hired the owner was the driver, mechanic, and everything else. Now that they have a driver they can focus on all the other roles and just ensure the driver is not crashing.

Read the first paragraph could tell it was AI written. Maybe if it was hand edited to be less AI I would have read more but it looked like the laziest Claude prose.

That'll be a no from me dawg.

I agree on the point of linking it, which the HN thread linked before supposedly had a link to the blog post in question but it did not have any content. So thanks for sharing nonetheless.

I've done similar, even to the point of a discord gateway integration that is very similar to the one Hermes ships with.

I still use Hermes because it's not a problem I care about solving right now and am spending my time and tokens on more important problems. I don't plan to always use it, and if anything it gives me ideas for what the ideal shape of what I want would be.

Also to add, having a unified space to chat with an agent that has a local system it can work with is quite liberating because I use it to drive my agent orchestration system. So I'm no longer bound to my computer or any one providers harness and whatever mobile solution they provide if any. It's been quite freeing and I don't use Hermes that differently than I would chatgpt, except it know exactly how I like to do my work and that means I have to remind it less.

Did you read it? Given it's all AI slop I wouldn't be surprised if not, but the claim is basically "I had this idea first, I think they stole it from me."

Not that they stole code or even copy, just the idea from a completely open source project (at the time).

Given how many people have posted and released similar systems over the time skills came out and even before, that's a huge claim with no substance to back it.

Those Python issues are things I had to deal with earlier last year with Claude Sonnet 3.7, 4.0, and to a lesser extent Opus 4.0 when it was available in Claude Code.

In the Python projects I've been using Opus 4.5 with, it hasn't been showing those issues as often, but then again the projects are throwaway and I cared more about the output than the code itself.

The nice thing about these agentic tools is that if you setup feedback loops for them, they tend to fix issues that are brought up. So much of what you bring up can be caught by linting.

The biggest unlock for me with these tools is not letting the context get bloated, not using compaction, and focusing on small chunks of work and clearing the context before working on something else.

This isn't mine, I found it posted on a gaming forum and thought it would be interesting to others here.