Skip to main content

Do I always sit in the same seat on the train?

I commute by train a couple of times a week. I catch myself walking to the same coach every morning without even looking at my ticket. The thing is, I never choose my seat; it's assigned automatically.

I think I sit in the same carriage and the same seat every time. Is this just some form of selective memory tripping me up?
I'm far too lazy to verify this myself, so I let Claude figure out whether I'm hallucinating or whether there's some truth to it.
It pulled data from roughly a hundred trips this year. On the 69 typical train configuration trips, I sat in coach 6 or 7 72% of the time. Those carriages have 68 and 55 seats. I usually sit in roughly the same area, and the funny thing is that the same seat keeps coming back: 16 different seats have repeated, and seat 20 in coach 6 and seat 8 in coach 7 have each come up five times.
So I was right! At least mostly.
The train I typically take has 7 carriages: two for the first classes, one restaurant car, and four normal carriages for me. One of them has cabins, one has a kids' area, and one has a pet area. As a solo traveler, that leaves me with one optimal choice, but they surprisingly often put me next to kids (not pets). So those exact coaches 6 and 7.
So I wasn't entirely right. The real answer is that I'm not fully hallucinating, and there's a perfectly good reason why I sit in the same area every time.
I also buy my tickets at about the same time every week. I usually book the morning train a day or two ahead, typically on the weekend around the same time (whoops, almost forgot to do it again!). I book the evening train the same day, a few hours before. VR, of course, fills the seats in a certain way, and the earlier I buy, the lower the seat number I get.
Sadly, VR doesn't remember me or give me any frequent-traveler service. A boring, predictable algorithm just does its thing.

Comments

Popular posts from this blog

Bird is causing high CPU on my macOS

There is no lack of people complaining about MacOS Tahoe, mostly about rounded corners and inconsistent design decisions. I have not paid that much attentention to that, but there is one mac bug i have paid attention to. It hasn't been a visual or ux but rather few system processes pegging the CPU. trustd , alongside with ecosystemd and ecosystemanalyticsd all reported high CPU usage. I can't exactly recall when this started, it might have predated my Tahoe upgrade but anyway, the trio of processes all had high CPU usage. Sure, it may have been the virtual efficiency cores and whether it affeced battery life or slowed down other processes i don't know to be hon...

I'm not a passionate developer

A family friend of mine is an airlane pilot. A dream job for most, right? As a child, I certainly thought so. Now that I can have grown-up talks with him, I have discovered a more accurate description of his profession. He says that the truth about the job is that it is boring. To me, that is not that surprising. Airplanes are cool and all, but when you are in the middle of the Atlantic sitting next to the colleague you have been talking to past five years, how stimulating can that be? When he says the job is boring, it is not a bad kind of boring. It is a very specific boring. The "boring" you would want as a passenger. Uneventful.  Yet, he loves his job. According to him, an experienced pilot is most pleased when each and every tiny thing in the flight plan - goes according to plan. Passengers in the cabin of an expert pilot sit in the comfort of not even noticing who is flying. As someone employed in a field where being boring is not exactly in high demand, this sounds pro...

Building a OTel sink that follows GenAI semantic conventions

I've been working on an OTel sink recently. To be more specific, it concerns receiving telemetry data from LLM interactions. Fortunately, there is a spec for all of this called GenAI Semantic Conventions . That is what I based my work on, so I can make assumptions about key attributes to highlight in the sink's UI, which is actually a CLI in my case. I dogfooded my handrolled sink using Pydantic AI (my favorite LLM framework), and all good, it follows the spec well. Key attributes flow in as specified. Pydantic AI also includes some of its own attributes, but that is expected. However, pick something like Claude Code, (via anthropic agent sdk), the reality is a bit different. It does not follow the spec at all. It has its own custom attribute layout . Same direction, different flavor with LangChain. The Python source has zero opentelemetry imports anywhere. None. The ls_* namespace ( ls_provider , ls_model_name , ls_temperature ) is its own thing, with LangSmith as the on...