As noted in the previous issue, week 50 was a bit of a dud due to me being rendered more or less completely out-of-service for 3 days or so. I only really felt up to some light work towards Thursday, which resulted in a tiny patch, at least.
Roadmap
I also continued something I had already started in week 49, namely filling the roadmap category with a bunch of additional entries. This recent batch came from a list I was curating over the past couple of months or so but hadn’t had the time to actually write down properly. There are a few more left that I’ll try to add over the coming days, primarily to round out the “HR section”.
Speaking of sections: Since the roadmap category has started to grow to a somewhat unwieldy size, I decided to add an overview post that provides a more structured - you guessed it - overview of the current items. Make sure to check it out, browse for topics you like, add your votes and - most importantly - feel free to start or participate in the respective discussions.
New Website
We got very few (actually…I think it was a single one) remarks on this, which is a very good sign: In week 49, we also released our “new old website”. It’s “new” because it’s now built on the foundation of our existing account management frontend. It’s “old” because we very consciously decided not to mess with the actual content too much as we had better things to do and are still unsure about what and how we want to present on there in the medium-term. But the old website was a technical mess and in utter need of replacement, so with some help from a freelancer for some of the frontend stuff, we got this taken care of as a “side-project” for the better half of 2024. Glad we were able to ship this well before the end of the year!
Illusive connection analyser bug
Last but not least, week 49 also had me chasing a bug affecting the connection analyser: A player reported that some connections that should work and do in fact show up in the ORS are invisible in the connection analyser. I couldn’t see any obvious issues or errors, so I tried to reproduce it using a 1:1 copy of the affected player’s routes. But to no avail: Locally, it worked just fine (what a software development trope…). As such, I am somewhat stuck on this.
This is where you come in: Have you experienced this problem before? Even “better”: Is one of your airlines affected by it right now? In either of these cases, please leave a comment below with details about the game world, airline and affected connection. Thanks a lot!
