HN user

TYPE_FASTER

1,700 karma

typefasterpls at gmail

Posts1
Comments942
View on HN

College radio is still a thing. I've discovered some good music via WRUV (UVM). WERS (Emerson College) dropped the Rockers reggae show when they changed their programming back in 2013, but I should try streaming again and see what it's like these days.

Are we watching the next sacrificial infra build-out happen (Global Crossing/Iridium), where eventually a bankruptcy will lead to affordability? Is this an artificial semiconductor demand peak with rapid expansion due to business FOMO? Will semi manufacturing ramp up to meet this peak, leading to a glut? Will this be like the pandemic supply chain whiplash impact on outdoor gear (Kona Bicycles at one point was offering a BOGO deal)?

Every once in a while, I have to figure out an IntelliJ indexing issue. I've got a personal Claude sub and access to Claude for work, so will not be using the JetBrains AI sub. If the indexing gets worse, or paying more for their AI becomes mandatory, I'll be done and back to Emacs, which is what I've been using for Claude anyway. Not there yet tho.

I asked a former truck driver once and his answer was that it's easier to see what's in front of you than behind you. I wondered why people in our neighborhood backed into their driveways at first, then I realized this was indeed true. If I turn into the street and back into my driveway, somebody probably hasn't jumped behind my car. If I get in my car and back out of my driveway, somebody walking/biking along may not notice my car backing out of the driveway, and my old potato backup camera isn't always the best at illuminating people behind my car at night in bad weather.

Yeah, I was surprised that something this obvious wasn't addressed.

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

I was working with Claude on a Chrome extension. The extension was getting a 429 "Too many requests" error on one website. Claude suggested a bunch of things to try, none of which really solved the problem and were kind of one-off attempts (hardcoded string compares, etc.).

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.

Biesma has asked himself why he was vulnerable to what came next. He was nearing 50. His adult daughter had left home, his wife went out to work and, in his field, the shift since Covid to working from home had left him feeling “a little isolated”.

I think social isolation can be a factor here.

Yes. Federal law requires retailers of drugs containing pseudoephedrine, ephedrine, and phenlypropanolamine to record the buyer's name and address and keep the records for two years (https://www.fda.gov/drugs/information-drug-class/legal-requi...).

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.

There is a difference between somebody who has used an algorithm/component/framework/library, and somebody who knows how to solve a problem using an algorithm/component/framework/library.

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.

Rule 5. Data dominates. If you've chosen the right data structures and organized things well, the algorithms will almost always be self-evident. Data structures, not algorithms, are central to programming.

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

For those who have been in the industry longer, why do you think it’s still important to stay strong in CS fundamentals?

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.