Agreed, I think the days of writing original code are mostly at an end, unless you are one of the lucky few working on the AI itself. And that may be short lived as well.

RFC/specifications are excellent as they convey the intent behind the code, which often isn't available or understandable by looking solely at the code. AI written code definitely needs tested for bugs or unintended pathways. One of the prompts I try to give AI is to document the code with comments. That seems to work pretty well for the most part, but my AI did recently put some comments in places that made the code fail to work, which is a rookie mistake.

LaZboy Logo

-----Original Message-----
From: Bruno Manzoni via Xymon <xymon@xymon.com>
Sent: Thursday, September 10, 2026 5:03 AM
To: xymon@xymon.com
Cc: Bruno Manzoni <bruno.manzoni@ubi-network.ch>
Subject: [Xymon] Feedback on using AI/LLMs for Xymon development and reviews

Hi everyone,

Here is my feedback on working with AI/LLMs for Xymon:

- We no longer code by ourselves; LLMs do it for us. The real skill now
is guiding the AI, designing the architecture, and validating the
result. LLMs write code better than even experienced C developers,
though skilled individuals��including good developers��are still essential
to direct them.
- We still need to write a specification, like an RFC.
- We still need to do reviews to catch problems that a good
specification or tests might miss.

All this changes the meaning of being a "code author" and shifts how a
team should be built.

Let me know what you think!

Cheers,
Bruno

_______________________________________________
Xymon mailing list -- xymon@xymon.com
To unsubscribe send an email to xymon-leave@xymon.com