kerpele

Not sure where your information that n8 was supposed to run Meego comes from, but I remember working with the Nokia s60 team already early 2009 and they were using n8 protos at the time. It’s definitely possible that there were two parallel projects though.

On the other hand, Maemo, the predecessor to Meego, required a pen-like pointer to comfortable use at the time as the UI elements were designed to be small. Only after they completely overhauled the UI (and renamed the Linux based OS Meego) it could have worked on the N8.

I’m not a ship engineer but I do know that ships are not built to be suspended from the ends. I guess in the worst case the hull breaks which would mean the canal to be blocked for quite a while.

Threatening the researcher really is the cherry on top here

Works again. I wonder if the fix was just rebooting a server

Wow, looks like triplebyte profile settings page is full of dark patterns. Like, setting yourself as not interested in offers will forcefully revert back after a time period, and that even though there’s a checkbox for opting in to being shown to companies you can’t save the profile without giving consent.

:(

Not sure if you were serious or not but your comment seems like a nice example of what the article talks about

> The main class of failures that I am worrying about regarding the MTTR is the very same observable problem that you solved last week occurring again due to a lack of quality gates. To the customer this looks like last weeks problem was not solved at all despite promises to the contrary.

I think the quality gates mentioned in the article are the ones where you have a human approving a deployment. If you have an issue in production and you solve it you should definitely add an automated test to make sure the same issue doesn’t reappear. That automated test should then work as a gate preventing deployment if the test fails.

Wow, this article made me realize I was a part of the very early generation game devs in Finland getting my first job in the industry in 2001. I was so young and naive then that I didn't understand how early it was.

Is it possible that the problem there is the amount of women starting studies in stem fields? I don’t have any numbers but anecdotal evidence of two Helsinki based schools in CS related programs had very lopsided gender ratios in bachelors and masters levels.

That's awesome!

Although, all copyrights are Apple's on that particular file. I wonder if everything's been done by the book.

If someone told the young Linux freak me back in the early 2000s that one day Internet Explorer’s rendering engine is based on the KDE rendering engine I would’ve probably died laughing and frozen in horror at the same time.

Yeah, I realize there’s probably nothing left if the old KHTML but it still does give me a chuckle.

I just realized my terminology was way wrong. Sorry.

You have Manhattan distance and you want Euclidean distance to make sure the path is always optimal. Execution speed should be the same or better in the average case with Euclidean distance.

Nice visualization!

I don’t think the algorithm is correct though. The heuristic seems to use Euclidean distance instead of “how the crow flies” and thus this implementation goes along the axis instead of directly towards the goal. This causes the algorithm to find the optimal route only occasionally and probably has little to no effect on average execution time.