3 ms·
They probably wrote the controller in JavaScript
by ajdude 3y ago
They probably wrote the controller in JavaScript
- pavel_lishin 3y agoAt my first job out of college, we were hired to create a point-of-sale system. We wrote it in Javascript, being unaware of how Javascript treats numbers. (Like a rented mule.) After the first few days, the client reached out and told us that the end-of-day numbers were sometimes off by a few cents - tax totals, things like that. After a few weeks, they'd be off by significantly more. Easily the most embarrassing incident of my career, even worse than when I accidentally left a `console.log("FUCK");` in production code as a debugging tool, or when we wrote some code to generate random four-letter codes that would spew out the occasional profanity.
- freedomben 3y agoWe had a similar issue with random four-letter codes. The simplest and easiest solution was to remove vowels from the pool of candidates. Consonant only codes are much harder to generate real words.
- Maxion 3y agoFCK!
- freedomben 3y agoThat's only 3 letters! FXCK was probably the closest we got with that change
- Freak_NL 3y agoNGGR and CVNT might not sit well in some countries either.
- selimthegrim 3y agoI once worked on software that interfaced with Omnipods just to read and display its data and it was an unholy assemblage of Java applets, Pascal, and out of date C#. (The software that is, I think the Omnipod DLL was just C)
- mmis1000 3y agoIt's probably caused by a shitty spec instead of bug. Some PM insists that you must sanitize the user input 'when' user inputs. And '.' alone isn't a proper number. Which led you to this. No. You should NEVER change user input when user action is not finished yet. That's a giant UX hazard.