Note that those are possibly photosensitive epilepsy risks if you turn them up to 60/100.

The article suggests (sensibly!) that the right thing to do is to actually go in and design what's being logged with purpose (i.e., everything should answer a known question). But I don't always know what I'm looking for when I'm testing a thing. At the risk of using LLMs as a hammer that hammers everything, I wonder if they'd help with that problem?

I've pointed Codex at Posthog logs, for instance, and it's been able to say, "yeah, well, look at this pile of residential proxies hitting your site." I wonder if it'd similarly be able to say, "hey, I notice a pattern where everyone who picks the Cleric class stops playing after level 3"?

There's a shallow, jokey purpose to it ("I could buy a BMW with this amount!"), but the real purpose is to demonstrate how we can do a better job of portraying a game catalog. I often wishlist stuff, then it pops up in a "Hey, it's on sale!" email months later. In that email, there's a banner capsule, but that doesn't help my brain remember why I added it.

To that end, after you get the bill, you get a nice, flat feed of stuff about all the titles you've wishlisted over the years. It's all stuff that developers painstakingly put together, but which Steam tucks away under the fold of a game's Store page.

Anyway, my wishlist came to about $250. My QA guy is up to $19k. Give it a go; hope you enjoy it!

Comments URL: https://news.ycombinator.com/item?id=48196207

Points: 3

# Comments: 0

His writing is often SO full of ideas that I can't absorb an entire piece in one sitting. It's like a 12 course tasting menu. The neat thing with his writing is that, despite what he says here about all 12 pieces being important together, you can often just pick an isolated bit and chew on it for a while, and still learn something.

(Presumably return to the other 11 courses later; they'll still be fresh.)

Another, where you can set cells and then have it solve: https://oskarstalberg.com/game/wave/wave.html

And an itch.io game where you are the wave function selector: https://bolddunkley.itch.io/wfc-mixed

I thought this concept would have found more traction in the world of procgen (in games), because it's pretty neat. But I found it difficult to work with, so perhaps others also did!

That video's great because it breaks down how Psygnosis managed to get 12 layers of parallax scrolling at 50fps and 128 colors on-screen. I never really loved the game as much as (say) Blood Money, but it was an awesome accomplishment in the same way demoscene demos were!

The inline examples have editable code, but that one's kinda nice because you can just tweak a few knobs.

HN folks are probably familiar with raster interrupts (https://en.wikipedia.org/wiki/Raster_interrupt) and "racing the beam." I always associated this with the Atari 800. You weren't "supposed" to be able to do stuff like https://youtu.be/GuHqw_3A-vo?t=33, but Display List Interrupts made that possible.

What I didn't know until recently was how much Atari 2600's games owed to this kinda of craziness: https://www.youtube.com/watch?v=sJFnWZH5FXc

It's stuff like this that makes me think that if hardware stopped advancing, we'd still be able to figure out more and more interesting stuff for decades!