Exploring Software Durability: Can Code Last 50 Years?
By
maraoz
Toasted golden, schmeared with insight. Top of the rack.
Summary
The article discusses the concept of software durability and the challenges of building apps that can last for 50 years. It explores the perspective of a programmer who reflects on the longevity of their code in various projects.
Key quotes
· 3 pulledCode I wrote for a Nuclear Power plant is still there.
Code I wrote for the steel mill is still in use.
Code I wrote to go into the DoD's...
You might also wanna read
Running Gemma 4 on a 2016 Xeon Server with No GPU: A Technical Walkthrough
The article describes running Gemma 4 (a 25B-parameter Mixture-of-Experts model) on a severely outdated server with a 2016 Intel Xeon E5-262
point.free·2h ago
NVIDIA Announces "Hack for Impact" London Event for Autonomous AI Agent Development
NVIDIA is hosting a "Hack for Impact" event in London, challenging participants to build autonomous agentic applications using open-source m
luma.com·4h ago
Four practical steps to control Azure Foundry token costs for agentic AI workloads
This article provides practical guidance on controlling token costs in Microsoft Azure Foundry, particularly for agentic AI workloads where
purplefrogsystems.com·5h ago
MerLean-Prover: A Recursive Agent Harness for Lean 4 Theorem Proving Outperforms Baselines
MerLean-Prover is an end-to-end Lean4 theorem prover that replaces 'sorry' declarations with kernel-checkable proofs using three agent types
arxiv.org·5h ago
Why small pull request policies can backfire on software quality
The article critiques a common software engineering policy that limits pull requests (PRs) to small sizes (e.g., 500 lines, few files). Whil
apenwarr.ca·7h ago
How Anthropic contains Claude's expanding access across its products
Anthropic describes how it has evolved its approach to granting Claude, its AI assistant, increasingly broad access to internal systems over
anthropic.com·8h ago