Feed aggregator
Google Takes a Snarky Shot at Apple Over RCS in Its Latest Ad
Read more of this story at Slashdot.
The New FineWoven iPhone Cases Are 'Very Bad'
Read more of this story at Slashdot.
DuckDuckGo CEO Says It Takes 'Too Many Steps' To Switch From Google
Read more of this story at Slashdot.
Windows 11 Gains Support for Managing Passkeys
Read more of this story at Slashdot.
MGM Resorts Computers Back Up After 10 Days as Analysts Eye Effects of Casino Cyberattacks
Read more of this story at Slashdot.
Microsoft Launches Surface Laptop Studio 2 With Upgraded Chips and Ports
Read more of this story at Slashdot.
Cisco Buys Splunk for $28 Billion in Massive AI-Powered Data Bet
Read more of this story at Slashdot.
Windows 11's Next Big Update Arrives on September 26th With Copilot, RAR Support
Read more of this story at Slashdot.
Rupert Murdoch To Step Down as Chair of Fox and News Corp After Seven-Decade Career
Read more of this story at Slashdot.
New Revelations From the Snowden Archive Surface
Read more of this story at Slashdot.
Waymo Begins Testing the Waters For a Robotaxi Service In Los Angeles
Read more of this story at Slashdot.
SpaceX Rocket Launches Starlink Satellites On Record-Breaking 17th Flight
Read more of this story at Slashdot.
Succesful Deployment
Typos are the bane of delevopers' existence. For most of our typos, the result is a syntax error. It's quick and easy to find and fix. But any time we're working with strings (or in languages where variables are declared at use) there can be many more subtle bugs.
So when Abigail's company sent an intern off to fix a few typos, they thought this was a lovely little low-hanging fruit bug to fix.
There were three typos which needed to be fixed.
return res.json({ status: "failurez", ... }); ... return res.json({ status: "succesz", ... }); ... Promise.all(data).then(()=> { resolve("succes"); ... });The intern made the changes and submitted a merge request. The request was reviewed, and the codebase was searched to make sure nothing was depending on those typos. Nothing was, so it was merged and eventually deployed. And that's the moment all hell broke loose.
Because while they checked their internal code to ensure that nothing depended on these misspellings, they had customers who consumed this API. While the documentation suggested that the customers should rely on HTTP status codes to determine success or failure, several customers didn't follow that advice and manually checked the status field, and thus depended on seeing "succes" or "succesz" in the output.
The shocking twist is that these customers were willing to update their code. Not to check the HTTP status codes, which would have required a rewrite of some logic, but to correct the spelling of "success".
[Advertisement] Keep the plebs out of prod. Restrict NuGet feed privileges with ProGet. Learn more.French Drillers May Have Stumbled Upon a Mammoth Hydrogen Deposit
Read more of this story at Slashdot.
Neuralink Is Recruiting Subjects For the First Human Trial of Its Brain-Computer Interface
Read more of this story at Slashdot.
Parents In US Offered Refunds For Purchases Kids Made In Fortnite
Read more of this story at Slashdot.
Airbnb's Naba Banerjee Reduced Partying By 55% In Two Years
Read more of this story at Slashdot.
FCC Plays Whack-a-Mole With Telcos Accused of Profiting From Robocalls
Read more of this story at Slashdot.
Amazon Is Set To Supercharge Alexa With Generative AI
Read more of this story at Slashdot.
Yelp Has a Wall of Shame For Businesses Caught Paying For Fake Reviews
Read more of this story at Slashdot.