makr17

I remember being in Tel Aviv for work, and pulling up maps to plot out a bike route from the hotel to the office. Only to find that the entire route is blurred out online. Turns out our office was a few 100 meters from something important to the IDF, so no map/route data available. Too far to reasonably walk, and didn't want to try a bike without knowing there was a reasonable route...

I still remember being "invited" to a meet-and-greet with the VP of Tech at my college after a fork bomb run amok. 17yo me was sure my academic career was at an end. He let me sweat for a few of minutes and then smiled and offered me a job. <whew>

I'm working on something similar. My biggest annoyance is that the overly-helpful LLM was making every die roll succeed. I ended up building some tooling around rolling dice. Also some tooling around character stats and inventory management, so those don't get lost in context compression.

Presumably stack depth and overflow.

I used to work somewhere that did that. Several of us in Eng pointed out that it was likely impossible to sell anything to DoD personnel since the reply would route internally. But I don't know if it was _fixed_, was still an issue when I left.

I remember in jazz class the instructor had a stack of jingles that showcased particular "weird" intervals. The only one I really remember now is the "Alway Coca Cola" jingle and a M6, but this was a _long_ time ago.

In the sitcom Mad About You there is an episode where Jamie tells Paul to put on a tie. Specifies the "navy blue one". "I don't own a navy tie." "Yes you do, it's the one that you think is dark green."

My wife and I go round and round about what is and isn't blue and/or green.

Coming up on 20 years ago I was building a system that was going to be deployed at various locations throughout a very large country. All locations had internet access; but the throughput, latency, and quality (e.g. packet drops) were all over the map.

For testing we ended up building a small linux box to proxy for the test environment in the office. We could throttle the throughput to any arbitrary level, introduce latency, and introduce packet drops. It's amazing how poorly a frontend will work when you throttle the network to 128kbps, and introduce a small percentage of dropped packets. But once you get the system to work (for some definition of "work") under those conditions you feel pretty good about deploying it.

Years ago I worked for a company that bought another company. Our QA folks were asked to give their site a once-over. What they found is still the butt of jokes in my circle of friends/former coworkers.

* account ids are numeric, and incrementing

* included in the URL after login, e.g. ?account=123456

* no authentication on requests after login

So anybody moderately curious can just increment to account_id=123457 to access another account. And then try 123458. And then enumerate the space to see if there is anything interesting... :face-palm: :cold-sweat:

My favorite example of this sort of thing has been In My Tribe by 10000 Maniacs. The UPC/Catalog Number remained the same between the 1987 release and the removal of Peace Train (track 7) in 1989. I have this memory of sifting through the stock at a large used CD store in the mid-90s hoping to find the pre-removal version.

> it was a good decade before they even admitted Perl 6 might take longer than expected

I was there at OSCon when Larry announced Perl6, and that it would be "out by Christmas". And I was there the next year, when he was asked about that, and cheekily replied "well, we never specified _which_ Christmas."

I feel like Bezos has well more than $10M, $1B/100 (centi). Perhaps you were looking for "hecto" (SI prefix for 100)?

A former manager once told me

> If you get fired, and didn't see it coming, that's a failure in management. You should have _plenty_ of explicit signs of where things are heading, starting in 1:1 and culminating in a PIP.