I fully believe the only sustainable future is that hot patching will need to itself become fully automated. Hot patch now with a minimal allowed amount of line changes to head off the AIs, review it in office hours for auditing and the team is actually awake.

My second belief is that environment variables as a development concept will need to be retired. If it's something that causes a security breach if it by its mere existence on a public git repo, it is information that by design cannot ever pass to a filesystem out of a chain of trust, not by mere development conventions people choose to adhere to.

▲

munificent an hour ago | parent | next [-]

> hot patching will need to itself become fully automated.

Great, even less control over the things we use and more power ceded to corporations.

	▲	Fordec an hour ago \| parent [-]
		Due to the small nature of hot patching (eg. bump this dependency, rotate these keys, turn off that config, follow the runbook) it will unlikely need to be a frontier model and is likely able to be done LocalLLM/Jev style decision making rather than having to hand all the keys to frontier model operators.

▲

stabbles an hour ago | parent | prev [-]

Hot patching is itself a liability

	▲	Fordec 24 minutes ago \| parent [-]
		Not reacting is a liability. Blue-Green deployment is a liability. Code is itself a liability. Choosing this career at all is a liability.