Skip to main content

The Reality of Long-Term Software Maintenance

2 months 2 weeks ago
When developers boast "I could write that in a weekend," they're missing the painful reality that haunts software maintainers for years. In a candid blog post, Construct developer Ashley explains why maintaining large software projects is a burden most programmers fail to appreciate. "Writing the initial code for a feature is only a fraction of the work," Ashley explains, estimating it represents just "25% of the total work" in Construct's 750,000-line codebase. The rest? A grinding cycle of "testing, diagnosing and fixing bugs, optimizing performance, upgrading it to work with other changes, refactoring, customer support, writing documentation and similarly revising the documentation over time." Ashley describes how accepting code contributions feels like someone offering to build you a free extension -- initially attractive until the roof starts leaking years later and the original builder is nowhere to be found. Meanwhile, your tenants (users) are furious, and you're stuck with "no good options." The post recounts Construct's own bruises: a community-contributed storage plugin still causing compatibility headaches a decade later, and third-party libraries that became maintenance nightmares after their creators vanished. These experiences explain why seasoned maintainers eye large code contributions with deep suspicion rather than gratitude. "If you suggest some software project uses some code -- even a small amount -- will you be there in literally 10 year's time sorting out all the issues that arise from it?" Ashley asks. "Usually the answer is no."

Read more of this story at Slashdot.

msmash

AWS Cat Qubits Make Quantum Error Correction Effective, Affordable

2 months 2 weeks ago

In a scene from the movie Gladiator, Roman emperor Marcus Aurelius, worried about the fragility of his empire, tells his general, Maximus: “There was once a dream that was Rome.  …

AWS Cat Qubits Make Quantum Error Correction Effective, Affordable was written by Jeffrey Burt at The Next Platform.

Jeffrey Burt

The New York City Subway Is Using Google Pixels To Listen for Track Defects

2 months 2 weeks ago
New York City's Metropolitan Transportation Authority and Google have successfully tested technology that uses smartphone sensors to detect subway track defects, the MTA said Thursday. The four-month experiment, dubbed TrackInspect, mounted six Google Pixel phones on four A train subway cars traversing Manhattan and Queens. The phones' accelerometers, magnetometers, gyroscopes and external microphones collected 335 million sensor readings and 1,200 hours of audio data, which were processed through 200 prediction models. The system identified 92% of defects later confirmed by human inspectors, including broken rails and loose bolts. "The goal with this [project] is to find issues before they become a major issue in terms of service," said Demetrius Crichlow, the agency's president. Following the successful trial, the MTA plans to expand to a full pilot where Google will build a production version for track inspectors.

Read more of this story at Slashdot.

msmash