3 ms·
> This explicitly programmed behavior can NOT be a bug Um, I know you said you work in software, and the rules say not to doubt you. So I'll press Y and move o
by pwinnski 5y ago
> This explicitly programmed behavior can NOT be a bug
Um, I know you said you work in software, and the rules say not to doubt you. So I'll press Y and move on.
There are so many levels of bugs that almost nothing would surprise me, and this falls very easily within the range of bugs I've witnessed personally. Let's try this:
Hahahaha. It takes a single off-by-one errors to accidentally increment prices. It would take a lot of effort to deliberate design a feature that deliberately adds to quoted prices on every refresh, for the purpose of... um... well, that part is unclear. This bug can NOT be explicitly programmed behavior, it's too obvious incorrect behavior to be something someone took time to implement.
Yeah, that was easy. Except mine makes sense.
- JumpCrisscross 5y agoThey may have never coded a pricing system. I haven’t, but I’ve coded trading systems. Typo a dividend or convert and your dumb little bot starts incrementing its offer every millisecond. (The fun is when another bot gets thrown into a complementary loop and the exchange yells at you.) Have a system that e.g. codes a local tax or maintenance allowance run on lookup, or have these data in two systems that try to sync but do it wrong, and you get something like this. (This is not a legitimate pricing strategy. Nobody gets FOMO buying an AT&T plan.)
- jklinger410 5y agoI think OP was saying that the price being relative to each user/session is not a bug, but a feature. The bug part is probably that it keeps raising the price on every refresh, rather than just once.