TYPE_FASTER

Then it broke, maybe I should have bought the warranty?

I bought a simpler model without wifi this time.

Also during the Dot Com era. Pretty much every cycle lead to more people getting into the field.

Investing in a visual redesign (Liquid Glass) but not an obvious UX issue of the notch hiding icons seems like a mis-prioritization.

I struggle to find content I actually want to watch. It's really weird.

I can't tell if it's me, or the content, or a combination.

I think part of it is our attention span, or lack thereof.

Eventually I asked it "hey, are you sending two requests when you could send one?" Claude thought about it for a minute and said, "you're right! Let me fix that." The 429 errors stopped.

I've found it really is more like pair programming than having another fully independent developer. For Jenkins pipelines, I don't care about hardcoded string compares as much. For the core capability of the software, details are important.

I think social isolation can be a factor here.

While there is no federal law restricting the sale of medications containing Dextromethorphan, a common cough suppressant, US states have started regulating sales of these medications (https://en.wikipedia.org/wiki/Dextromethorphan_regulation_by...). It looks like most of the time, it's an 18yrs and up age restriction.

My guess would be that it's easier for company policy to always scan the ID, even for age verification, instead of having different policies depending on what is being purchased.

In the beginning, you need the person who knows how to solve the problem. They are harder to find.

If you are pressured to grow quickly, you might be tempted to lower the bar. You can, as long as you understand that the person who knows how to solve the problem is still critically important, because they will be telling people which algo to use.

I think every company that uses tech needs at least one of these people to start with.

Also see: SharePoint

If I have learned one thing in my 30-40 years spent writing code, it is this.

Software abstractions have always made it easier to build software without having to understand the inner workings of the mechanism that has been abstracted. But that doesn't mean we don't have to understand how it works.

I saw this happen frequently with cloud infrastructure. Cloud services remove the physical and organizational barriers associated with building and scaling infrastructure. But you still have to understand networking to manage your network infrastructure in the cloud. When it doesn't work, you can talk to AWS Support, but they are there to support AWS services, not design your network for you.

The Java Streams API makes it easy to write fluent code. But the Streams API doesn't make that code efficient for you. You still have to think about the cost of each step in the fluent chain, and the optimal order. Does it make sense to sort and then filter, or filter and then sort? Think about it.

I was working on a Chrome Extension with Claude. The extension kept getting rate limited immediately on one site. Claude suggested a few approaches, but nothing was working. Then I realized, wait, "are we sending two requests for the content when we could be sending one?" "Yes, let me fix that." Dude.

Commercial airline manufacturers have been working on automating every step of the process for decades. But pilots still have to know how to fly the plane, and troubleshoot when things go awry.

We still have to understand O(n) notation and how it applies. We still have to understand distributed systems.

We still have to know how to fly the plane.

Not sure I agree. I remember e-mails being capitalized and punctuated.

It's not so much typos and laziness as much as incomplete thoughts and distraction. Communication as a whole has devolved from an e-mail with a complete thought and some details to a text or chat message without capitalization, punctuation or context.

The lack of capitalization and punctuation are just a tell to me that the sender didn't put thought into it.

I can't tell you how many times I get a chat message asking a question. I in return ask questions about context, and explain why I'm asking. Then the original sender gets annoyed and provides context. Then I ask more questions. Then the original sender gets quiet. Then I get an invite to a meeting to discuss with a wider audience.

I have a virtual instance of Win11 ARM running in UTM on my MBP. It's honestly been surprisingly rare that I have to figure out how to run something that requires x86. More and more Linux distros have an ARM version that I can run if I need to.

This is so true.

He was so funny. I need to watch some of his other films.

I didn't know about about this film. Thank you!