> None. Wouter is aware of everything and disappointed by most of it.

Here I am, brain the size of a planet and they ask me to take you down to the bridge. Call that job satisfaction? ’Cos I don’t.

But I've also seen my fair share of "trains in this direction won't recover for hours" over the years, and directly after such an incident, the official systems usually don't really adapt all that well. I don't know if they're "massaged" manually after that or if it's just a case of the entire system finally figuring out that an entire station is FUBARed, not only one or two scheduled connections…

The SBB timetable app and website can become really unhelpful if there has been an "accident involving a person" [0]; other than that, I've got little issues with them day to day.

But it seems your model doesn't have a way to know that the IC from Biel to Olten goes through Grenchen (it only presents the obvious routes that wouldn't work in this case).

[0]: https://company.sbb.ch/en/railway-development/services-rus/r...

But I suspect the positive opinion on Lua stem more from the standardized environment the language is built around (i.e. how it is embedded into applications): If you don't explicitly pass capabilities like file handling etc. into the script, it CANNOT use them. Sooo many scripting languages get this wrong, it's actually embarassing.

Edit: Also, if you're looking for earworms and like loopy melodies, check out David Fenn's Soundtrack for Moonlighter: https://davidfennmusic.bandcamp.com/album/moonlighter

Especially "Macadamia Mayhem" and "Restless Roots" tend to follow me around for hours each time I revisit the album :)

…should make for an interesting SCP story :)

I can also do nothing at scale just with a hammock :)

This reminds me of "Youth without God" by Ödön von Horváth:

> Perhaps Anne’s mother was right. Perhaps men are mad now—those who aren’t mad haven’t the courage to put their maniacal fellows into strait-jackets.

SCNR :)

Sounds like a good situation for the litany of percussive maintenance.

> - CT and MRI data processing

> - scheduling systems for universities and other schools (makes education more scalable)

Those two read as if they are of different urgency (#1: whoever needs it urgently is at risk of dying, schedules for "non-urgent" cases will be affected for months, turning many into urgent cases; #2: the education systems will suffer, but it only gets dire after multiple days), until you realize that #2 also applies to e.g. hospitals.

Medicine at scale is already barely scraping by as it is (see: overworked staff etc. etc.), but disrupt the internal IT working of hospitals and the indirect body count will rise fast.

I vote for "end of unit" (ASCII 0x1F).