fzaninotto

I had the same problem. Restarted Claude Code after an update, and now it has disappeared.

To reduce token count on command outputs you can also use RTK [0]

[0]: https://github.com/rtk-ai/rtk

Just before the end is this one-liner:

> the same input can map to more tokens—roughly 1.0–1.35× depending on the content type

Does this mean that we get a 35% price increase for a 5% efficiency gain? I'm not sure that's worth it.

fzaninotto

4 ay öncediscuss

Instead of focusing on the top 20 files, you can map the entire codebase with data taken from git log using ArcheoloGit [1].

[1]: https://github.com/marmelab/ArcheoloGit

fzaninotto

5 ay öncediscuss

Is "Agentic Engineering" is the new name for "Agent Experience"? If so, and even though I love Simon's contributions, there are many other guides to making codebases more welcoming to agents...

Shameless plug: I wrote one. https://marmelab.com/blog/2026/01/21/agent-experience.html

fzaninotto

5 ay öncediscuss

Thanks Hacker News for surfacing such jewels, and kudos to the author for such a great piece.

Although I will never use anything of what I learned from this article, I feel a better person since I’ve read it.

In one of the alternate universe I like to imagine, AI slop doesn’t exist and the Internet is filled with gorgeous pieces like this one.

fzaninotto

5 ay öncediscuss

I don't agree with the premise that we pay a subscription because there is no better and cheaper alternative. We pay Slack subscriptions but we could get IRC for free. We pay Google Drive subscription but we could get rsync for free.

The reason we pay a subscription is because the company that built the software knows our business, knows how to get in touch with the decision maker, and knows how to market their product as something desirable. The actual software has little influence in that decision.

On the contrary, I think the price of SaaS subscriptions will go up as a result of AI. Because the only customers who will switch to a cheaper (or home made) alternative are the ones for whom the software is a commodity. These customers used to form the long tail of subscriptions, usually on the lower tier. When the entry pricer disappears, and the software editor has to generate a high return for their investors, the only way to keep profitability is to increase the price for the other tiers.

fzaninotto

6 ay öncediscuss

I agree this could be a template that services like GitHub should propose, the same way as they suggest contributing and code of conduct templates.

fzaninotto

7 ay öncediscuss

I think this article misses the most important point of MCP: Authentication. Granted, it wasn't in the initial spec, but it is now, and it really opens interoperability without compromising on security.

Think about how to provide your SaaS service to users of ChatGPT or Claude.ai (not only coding tools like VSCode). At one time, the user will need to allow the SaaS service to interact with their agent, and will have to authenticate in the SaaS service so that the agent can act on their behalf. This is all baked in the MCP spec (through OAuth) [1], and scripting can't beat that.

That's why the Extensions/Applications marketplaces of consumer AI assistants like ChatGPT Apps [2] are a thin layer on top of MCP.

Another domain where MCP is required is for Generative UI. We need a standard that allows third-party apps to return more sophisticated content than just text The MCP spec now encloses the MCP Apps specification [3], which is exactly that: a specification for how third-party apps can generate UI components in their response. On the other hand, scripting will only let you return text.

[1]: https://modelcontextprotocol.io/specification/2025-03-26/bas... [2]: https://help.openai.com/en/articles/11487775-apps-in-chatgpt [3]: https://github.com/modelcontextprotocol/ext-apps

fzaninotto

8 ay öncediscuss

I've closed my share of AI-generated PRs on some OSS repositories I maintain. These contributors seem to jump from one project to another, until their contribution is accepted (recognized ?).

I wonder how long the open-source ecosystem will be able to resist this wave. The burden of reviewing AI-generated PRs is already not sustainable for maintainers, and the number of real open-source contributors is decreasing.

Side note: discovering the discussions in this PR is exactly why I love HN. It's like witnessing the changes in our trade in real time.

fzaninotto

8 ay öncediscuss

Hi, author here.

I love reading the posts in this thread. It seems the waterfall vs Agile debate is still vivid in the HN community, which surprises me.

I know that developers have different experiences with SDD, and there is no one-size-fits-all methodology anyway. It's interesting to read the feedback of people who really like it, especially when they describe their background and the type of project they use it for.

In my experience, SDD doesn't bring any value as I'm already using Plan mode before going to implementation. I have also never seen instances of a coding agent doing exactly what I had in mind in the first try (except for very simple cases), so there must be iterations, which defeats the purpose of the Big Design Up Front.

Finally, I really think coding agents pave the path for a new way to develop digital products, more productive and closer to the users' expectations. But I doubt that SDD lies anywhere in this path.

fzaninotto

9 ay öncediscuss

Great feedback from the Etsy team about a real-world LLM usage that proved efficient.

fzaninotto

12 ay öncediscuss

This new browser mode is a robot that replaces visitors on websites. It can't be good news for website editors...

Should we (developers) start building websites for robots?

fzaninotto

geçen yıldiscuss

This looks similar to React application frameworks like react-admin [1] or Refine [2]:

    const App = () => (
      <Admin dataProvider={dataProvider}>
         <Resource name="posts" list={PostList} />
      </Admin>
    )
    
    const PostList = () => (
      <List>
        <DataTable>
          <DataTable.Col source="date" />
          <DataTable.Col source="title />
          <DataTable.Col source="author" />
        </DataTable>
      </List>
    );

The article mentions XML, but the true revolution is JSX itself, which lets you describe any piece of logic as a React element. This opens the possibility to create DSL for everything, just like in Python.

[1]: https://github.com/marmelab/react-admin [2]: https://github.com/refinedev/refine

fzaninotto

geçen yıldiscuss

Congrats! Now you need an entire datacenter to visualize a web page.

fzaninotto

geçen yıldiscuss

This is nice, but I wonder about the actual use cases of such a service, given the very loose permissions:

1. Anyone can subscribe to a channel 2. Any registered user can publish to a channel 3. Only registered users can publish to their personal channel (@username)

The second point in particular is problematic. I don't want to add notifications to my app, only to have a script kiddie use is to spam my users.

fzaninotto

geçen yıldiscuss

OP is making a decision about a complex problem using only back of the envelope calculation and without looking for scientific studies on the matter. We’re not obliged to take their advice. Typing “AI Carbon Footprint” on Google Scholar brings much better info than this post.

fzaninotto

2 yıl öncediscuss

Evaluating the quality of the responses of AI agents used to be tricky. It required knowledge of eval criteria as well as third-party tools like promptfoo, ragas or prometheus. Now openAI makes it ridiculously easy with a new API endpoint. It can grade a completion against a reference response, assess its format and tone, and you can even promt the eval to add your own criteria.

fzaninotto

2 yıl öncediscuss

It seems to be unable to solve hard sudokus, like the following one where it gave 2 wrong answers before abandoning.

+-------+-------+-------+ | 6 . . | 9 1 . | . . . | | 2 . 5 | . . . | 1 . 7 | | . 3 . | . 2 7 | 5 . . | +-------+-------+-------+ | 3 . 4 | . . 1 | . 2 . | | . 6 . | 3 . . | . . . | | . . 9 | . 5 . | . 7 . | +-------+-------+-------+ | . . . | 7 . . | 2 1 . | | . . . | . 9 . | 7 . 4 | | 4 . . | . . . | 6 8 5 | +-------+-------+-------+

So we're safe for another few months.

fzaninotto

2 yıl öncediscuss

It can solve sudoku. It took 119s to solve this easy grid:

_ 7 8 4 1 _ _ _ 9

5 _ 1 _ 2 _ 4 7 _

_ 2 9 _ 6 _ _ _ _

_ 3 _ _ _ 7 6 9 4

_ 4 5 3 _ _ 8 1 _

_ _ _ _ _ _ 3 _ _

9 _ 4 6 7 2 1 3 _

6 _ _ _ _ _ 7 _ 8

_ _ _ 8 3 1 _ _ _

fzaninotto

Submissions

Show HN: UX Quest

What makes multi-agent coding work

Vibe-Spec: Generate Specifications from Coding Agent Logs

Using LLMs to classify unstructured listings

AI Coding Assistants Are the New Compilers

Get-current-day (NPM package)

Reliable AI Agents: Mastering Eval

LLMs Are the CPUs of the AI Era

OpenAI Eval

New client-side hooks coming to React 19

EU Declares War on GreenWashing

Documentation: The Key Enabler for Open-Source Success

Anatomy of a Profitable Open-Source Project

Show HN: Molly, a chatbot showing signs of consciousness

Building Artificial Consciousness with GPT-3

Is React Having an Angular.js Moment?

Client-side full-text search in CSS (2013)

Using Copilot to review code and fund Open-Source projects

React without useEffect: Just use a framework

Multi-Tenant Single-Page Apps: Dos and Don'ts

comments