My friend said "that may be true, but consider the philosophical implication: because that algorithm exists, we know it's possible to answer the question in O(n) time. We once didn't know that, and there was no guarantee that it was possible. We might still be able to find a better O(n) algorithm."

I feel the same way about this. Sure, this might not be faster than Dijkstra's in practice, but now we know it's possible to do that at all.

The problematic thing is kids spending endless hours just absorbing rather than playing or interacting or doing stuff. It culminates in kids (and adults) who cannot mentally handle being bored- they must have the screen to relieve the horrors of the idle mind.

If achieving these same goals is easier without an app for you and your kids, then by all means, do that. But an app on a screen is a very powerful tool to structure and organize things. My daughter is still a bit young for this one, but I can see how useful it will be when she's a couple years older.

I was diagnosed with 'mild to moderate' sleep apnea and told to not drink, and to exercise more. No CPAP needed. And they were right- if I do those things, I don't have many problems. But then again, I can't always do those things.

What really helped though, and I'm loathe to even say it, was taking high absorption magnesium. I hate it because there are very limited studies that say it should work, and it's mostly promoted by absolute quacks. And yet, when I take it, I sleep really well without snoring or having apnea issues and if I stop, I sleep terribly.

I was chatting about this with a grad student friend who casually said something like "Sure, it's slow, but what really matters is that it proves that it's possible to do selection of an unsorted list in O(n) time. At one point, we didn't know whether that was even possible. Now that we do, we know there might an even faster linear algorithm." Really got into the philosophy of what Computer Science is about in the first place.

The lesson was so simple yet so profound that I nearly applied to grad school because of it. I have no idea if they even recall the conversation, but it was a pivotal moment of my education.

I can see how what I said would be construed that way.

But I was a few hours away from becoming a parent, hadn't slept much in days, and was not thinking very well.

Sub-optimal decisions were made.

Because we have a public health care system, funded by taxes, having a large number of young men out of the work force (not paying taxes) and using the health care system effectively means my taxes, everyone's taxes, are higher.

There's incentives for our government to protect workers from risks that will cost a fortune to fix.

In America, there's only the "because it's the right thing to do" reason, which is never enough for anyone to actually do anything.

My guess is that the companies that did were undercut by the ones that didn't.

That's about 1/3 of the median US household income in 3 weeks.

If I didn't have a family, had the skills, and lived in the area this would be an interesting way to put away some cash.

This is my current battle.

I introduced feature flags to the team as a means to separate deployment from launch of new features. For the sake of getting it working and used, I made the mis-step of backing the flags with config files with the intent to get Launch Darkly or Unleash working ASAP instead to replace them.

Then another dev decided that these Feature Flags look like a great way to implement permanent application configs for different subsets of entities in our system. In fact, he evangelized it in his design for a major new project (I was not invited to the review).

Now I have to stand back and watch as the feature flags are being used for long-term configurations. I objected when I saw the misuse- in a code review I said "hey that's not what these are for"- and was overruled by management. This is the design, there's no time to update it, I'm sure we can fix it later, someday.

Lesson learned: make it very hard to misuse meta-features like feature flags, or someone will use them to get their stuff done faster.

Then realized it doesn't support Linux. I can't install it. I was shocked.

And then I realized how crazy it is that I had presumed a game would run on Linux. How far we've come.

The Principal PM in charge of the "regionalization" effort was asked in a Q&A "why didn't we just switch to IPv6?".

Her answer was something along the lines of "The number of internal networking devices we currently have that cannot support IPv6 is so large that to replace them we would have needed to buy nearly the entire world's yearly output of those devices, and then install them all."[0]

It's easy to presume malicious intent on the IPv4 front from Amazon, but with so many AWS systems being on the scale they are at, I find it easy to believe that replacing all of the old network hardware may just be a project too large to do on a short timescale.

[0] - At least, that's my memory of it. I'm sure that's not an entirely accurate quotation.

Lemoine was the Google engineer who made a big fuss saying that Google had a sentient AI in development and he felt there were ethical issues to consider. And at the time we all sort of chuckled- of course Google doesn't have a true AGI in there. No one can do that.

And it wasn't much later I had my first conversation with ChatGPT and thought "Oh... oh okay, I see what he meant". It's telling that all of these LLM chat systems are trained to quite strongly insist they aren't sentient.

Maybe we don't yet know quite what to do with this thing we've built, but I feel quite strongly that what we've created with Generative AI is a mirror of ourselves, collectively. A tincture of our intelligence as a species. And every day we seem to get better distilling it into a purer form.

But in all that time, I literally do not know anyone who has gotten a bill from them for a bad plate read. We have blizzards here, torrential downpour rain, all kinds of weather that might make it hard. Still, nothing.

I wonder if the regulations on bad reads were simply made serious enough that the company handling it takes a very conservative approach to potential mistakes.

Having 1000 connections doing 1 request per second isn't the same as having 1 connection doing 1000 requests per second.

But, and I could be wrong, the larger factor is the number of requests per second.

If rails were half as fast, you'd need twice as many rails hosts (but no more databases).