"It works, don't touch it" - the most dangerous phrase in tech in 2026

A viral post is making waves among CTOs: the old wisdom "if it ain't broke, don't fix it" has become the best enemy of survival in the agentic era.

The fact

A widely shared post (top HN this week) elevates to a rule a shift that has been felt since mid-2026: in an environment where agentic AI and production automation rely on instrumented API call chains, an app "that works but has never been touched" becomes a liability - not an asset.

Our analysis

The pitch: the useful automation surface goes through structured logs, up-to-date OpenAPI schemas, documented webhooks, OpenTelemetry traces. A 2018 monolithic app, in Rails 5, without tracing, without a stable API schema - even if it generates cash - becomes impossible to consume by an agent. Result: your "working" stack blocks your "learning" stack.

The related thread (see #1009, Gartner thesis "SaaS-is-over"): legacy SaaS will be bypassed by agents that connect directly to raw data - except those that offer an agent-friendly API. The same CTOs who protected their monolith "because it runs" will wake up with an obsolete asset in 24 months.

To nuance: do not confuse "modernize" and "rewrite". The real investment is instrumentation (tracing, schemas, API contracts), not a from-scratch rewrite. A well-instrumented monolith is better than ten microservices without logs.

To watch

• The peak of "agent-ready API" announcements from legacy SaaS (Salesforce, ServiceNow, SAP) in H2 2026.
• The first major production incident caused by an LLM agent connected to a poorly documented API - it's a matter of months, not years.