News for hackers. Stuff that matters.
Re:Why senior developers fail to communicate their expertise by nine_k on Tuesday May 12, 2026 @03:25PM (#48113176)
Innovation is change, and change is the opposite of stability.

Innovation can reduce pain though, if the current pain is strong enough. A stable stream of failures in production can be the kind of "stability" you want to disrupt.

Re:Why senior developers fail to communicate their expertise by lnenad on Tuesday May 12, 2026 @04:11PM (#48113808)
What are we talking about? Philosophically yes. Factually, no. In the context of a system innovation could be switching from one form that renders in 1 second to another that renders in 50ms. Stability isn't part of that equation.
Re:Why senior developers fail to communicate their expertise by nine_k on Tuesday May 12, 2026 @04:38PM (#48114197)
Is this switching risk-free? Consider all these ancient computer devices that run high-stakes equipment for years and decades without change. An RPi could replace an ancient PDP-11, cost a fraction, consume a fraction of energy, be faster, etc. But it also may introduce new and unknown failure modes.
Re:Why senior developers fail to communicate their expertise by mpyne on Tuesday May 12, 2026 @04:22PM (#48113991)
Being able navigate change can provide stability in the long term though, at least as opposed to being resistant to change.
Re:Why senior developers fail to communicate their expertise by nine_k on Tuesday May 12, 2026 @04:33PM (#48114141)
Yes, all stability in real life is metastability, it needs a constant effort to maintain. A worthy innovation can lower this effort, or lower the risk of a catastrophic failure.

A complete stability is death.

Re:Why senior developers fail to communicate their expertise by mnsc on Wednesday May 13, 2026 @01:27AM (#48118181)
Resistance to change is very different than reluctance of change.