I've been gradually switching a few things over to Namecheap in the past year, but my motivation has nothing to do with their prices. Its more that they're one of the few registrars that's mostly trying to just be a registrar and doesn't constantly shove ads for their value-add services in my face to the point that I want to vomit.

I'd gladly pay more for a service that just stays in their lane and sticks to what I actually want to pay them for.

But even when its caused by debris, the actual leak may still be slow enough that a pressure sensor can catch it in time to drive to a tire place at one's convenience and get it taken care of properly.

I find it interesting that "knowing how to change a tire" is such a big deal for so many people. Nobody ever taught me how to do it. I just found myself in a situation where it needed to be done, opened the car manual, and kinda just figured it out. The hardest part was figuring out how to unpack the folded up jack that came with the car, because I think that was the only bit that wasn't covered by step-by-step instructions.

Old 78s is a perfect argument for why copyright needs to expire. The record companies aren't preserving this old recordings but they are using the copyright hammer to prevent others from doing it for no damn good reason.

The longest a copyright should last is life of the artist plus 10 years. And there are solid arguments for it being much less than that. If a corporation registers a copyright, they must name a single principle artist for this benchmark.

Measure my productivity by lines of code. I can pump shit out at a phenomenal rate. But it's going to be exactly that: shit.

I'm paid to solve problems. Sometimes a problem requires me to change a single variable. But finding that single variable could take hours, sometimes days. Debugging is often a time consuming process.

I did. But I had my PC made to order, so every single item was listed in the invoice.

"Most" !~= "All", and there's always a long tail. Sometimes the most critical software for users is some niche application that can't be bothered to update to deal with new compatibility issues.

And sure, Microsoft might create-and-abandon libraries all the time. But all the old libraries still work.

Only Apple has the luxury of actually breaking compatibility with new versions of their OSes, and that still causes problems with people who use software from stodgier companies that aren't part of the Apple RDF.

I blame this entirely on the design philosophy of many turn-by-turn navigation systems. That is to keep you as ignorant of your surroundings as technically possible, until 5 seconds before you need to make the next turn... If you're lucky. That's why I can't stand many such systems.

But its also why I really like the system Tesla puts in their cars. In addition to the usual turn-by-turn stuff, they also show you two things everyone else tries really hate to hide: A list of your next navigation steps, and a big top-down map showing your route. It actually gives you some situational awareness.

(* Yes, I know there are people who will complain about the actual directions. There are people that will complain about any implementation of that if its not perfect for their specific area in comparison to some other implementation they like better. But it works fine for me, and that big map means that its useful even if its not giving me turn-by-turn instructions.)

Combined with "WHY WON'T YOU SHOW ME ALL THE STORES IN THE SHOPPING CENTER I'M FOCUSED ON?!?!?".

I know designers love to reduce information density to make things look cleaner, but sometimes it can have a massive negative impact on the actual utility of the product.

This happens with everything Google does. When they come out with a new product, they have enough of a technical advantage that they're far superior than any competition can ever hope to be. This is such a lead, that the competition doesn't even try unless they serve some niche market.

Then, years later, Google loses interest in that product and it starts to go stale. But its still good enough that the competition never really takes off.

Then it finally goes poof, and everyone is scrambling to find an alternative, but nobody is actually prepared to take over.

Instead of using taxpayer money to pay off the service providers, open up the market. Stop letting cable be a monopoly and let the market fight it out.

Or just slap a cap on what these monopolies are allowed to charge.

When I'm doing something new or interesting, I often end up building it three times:

1. Build the critical functionality as throwaway code just to see if I can make it work
2. Build out the full system to get a feel for how all the pieces fit together
3. Rebuild the full system now that I understand it well enough to properly architect it

Of course depending on the circumstances, I may wind up combining two these iterations with refactoring, or not doing all of them on every project.

Unless you point a spectrometer at them.
Then they often have a huge blue spike, followed by a big dip, and then a gentle curve.
Or if you're lucky, and find one of the few brands that can do better than this, you still have at least a small dip after the blue. And regardless, the spectrum curve is always a bit spiky and uneven.

So sure, for normal everyday lighting purposes, you're absolutely correct.

But if you actually need something whose output can be modeled by a blackbody radiation spectrum, then not so much. Sure, most of these cases fall in the realm of scientific experimentation and material analysis, but they do still exist.

I wonder what percentage of that 10k can prove Japanese ancestors. I bet it's a significant portion of the total.

There are third generation immigrants in Japan who can not gain citizenship. If you are not Japanese, you can not be a citizen.