Why Write Code in 2026

Re:Why Write Code in 2026 by jurgenburgen on Sunday July 12, 2026 @04:49AM (#48879485)

> For LLMs to be really helpful, they have to take over complete maintenance of the code. So you can treat them like an external library: Just assume it works.

We already tried this with humans. It works so poorly that it got the derogatory name “ivory tower architect”. It usually results in theoretical designs that are unworkable in the actual system, implementation teams (or LLMs) that work around the architecture and a lot of slowing down of velocity as the architect and implementers argue past each other.

[ Parent | on HN ]

Re:Why Write Code in 2026 by zelphirkalt on Sunday July 12, 2026 @05:32AM (#48879693)

This happens when the architect is out of touch. If the architect themselves works on the code, writes code, deals with the imposed restrictions, then the chances of that happening is much lower. Assuming, that they are a good architect.

[ Parent | on HN ]

Re:Why Write Code in 2026 by jurgenburgen on Sunday July 12, 2026 @05:43AM (#48879750)

I agree, if the architect participates in the implementation then they avoid this anti-pattern. That’s not compatible with hands-off autonomous agents where you treat implementation as a black box.

[ Parent | on HN ]