jharger

I used to do this at the beginning of a game as a kid, because the earthquakes were pretty harmless without buildings to knock down. You'd just load up on cash, then start building!

Not the poster you replied to, but I've been thinking of it lately in a different way. Functional tests show that a system works, but if a functional test fails, the unit test might show where/why.

Yes, you'll usually get a stack trace when a test fails, but you might still spend a lot of time tracing exactly where the logical problem actually was. If you have unit tests as well, you can see that unit X failed, which is part of function A. Therefore you can fix the problem quicker, at least for some set of cases.

It could be that this sort of thinking contributes to the massive number of JS frameworks out there. You think React is bloated, so you make a "React in 70 lines" ... realize there's some things you missed... fast forward to two years later and you've got another framework.

Speaking of Jazz Jackrabbit, I always enjoyed seeing the poster in Fortnite when I used to play it.

We used to do a "feely score" of 1-5. It sort of worked to gauge how the team felt (positive or negatively), but it eventually devolved into everyone arguing over whether 3 or 4 was the baseline for an unremarkable day.

I live in Albuquerque, and this sort of thing varies greatly around here. There are certainly places that are $35-50 for a hair cut and require appointments, but there are also barber shops and chains where you can walk in and get a haircut right away for $10-15.

Why not have optimized versions that use native instructions when available, and then fall back to the portable version when they are not?

Back when I worked there (mid-late 90's) the chick-n-strips were actually marinated in the same stuff as the Chargrilled chicken sandwich. Both items are no longer on the menu, and were vastly superior to their offerings today, IMHO.

Do you have an article or book you can link to on the subject? I'm very curious why there wasn't much demand for wheeled luggage until the 80's.

Is it because people flew less? Because more people checked luggage more often and carry-on was less common? Because airports were smaller?

I remember implementing this for a class years ago, and then the professor suggested doing the inverse to try to expand the image width. The idea was you would duplicate the lowest energy seam... but all that did was create a lot of repeats of the same seam.

I never did finish that weird idea, but I probably needed to try something like increasing the energy of the chosen seam (and its duplicate)... I may try that again, just because I'm curious what would happen.

I'm curious what causes that strange phenomenon. You had a 50-50 chance to get it right, but it's the wrong way almost every time.

Except fixing the rebase issue isn't usually that difficult, if you know about reflog.

What about a chain of airships?

One supermarket I went to tried that... but the user experience is so awful that no one wants to do it, so the scanners just sit at the entrance, lonely and unused.