Highly recommend it. I think we should make a .well_known url for them or something, honestly.
10,730 karma · joined March 29, 2007
PDX/OR/USA
justin dot george a@t gmail.com
"Full stack JS" since 2001
Highly recommend it. I think we should make a .well_known url for them or something, honestly.
I bought one of their TVs in 2019, it's fabulous if your criteria is "turns on, displays what is connected to its inputs, and has decent video quality", and nothing more. I would recommend them heartily, if you can get access to one.
The idea that every crash isn't acted on is kind of a crazy one, to me. Not every crash is actually actionable in e.g. a mobile app, but every one should at least get an eyeball in my opinion.
This, to me anyway, is the bare minimum of "caring about software quality". If you do this regularly you'll have very solid code, and it's interesting that I have the perception at least that Guild Wars was a quality product.
There's another layer, where you do that for subthreshold issues like UI inconvenience, etc, but that's bonus, I think.
strong exponential time hypothesis, and the titular exponential time hypothesis
It's not saying that these problems are easy, but it does demonstrate that they are much easier than previously believed. A decade ago if a human had published this kind of thing, and importantly if it held up, they would be almost certainly a strong candidate for some sort of award(s).
The primary users of any API are the designers and engineers of the applications that use it. How many laypeople know what Postgresql is? How many of the applications they use run on it?
Where else would you go? I'm honestly scratching my head thinking of someplace that wouldn't run you out on a rail, but that would give serious feedback. Kernel mailing lists are out, maybe there's something like that which I can't remember off the top of my head, but...
Also, nomenclature is incredibly hard. There are only two hard problems in computer science: cache expiration and naming things.
Companies in industries where you can print money (for a while...) usually haven't actually been put under any duress, so any fool can manage them and look like a genius. It's in hard times that you discover whether you're a good manager or not, when the decisions made in good times come home to roost.
You have to treat them like an ignorant junior engineer in nearly every respect, but trying to match with them at programming per se is a fool's errand.
The reason to read the code is not because you can catch their errors in programming. It's because they may have missed the forest for the trees at the operational or strategic level, and so that you can learn from them to understand better. It's like trying to beat the engine in chess now.
You'll see a golfer perform at least a few strokes different depending on their partner, and at a pro level that's the difference between "in the money earning an extravagant living" and "washed out on day one, thinking about taking a different job"
Also maybe I'm a curmudgeon but I generally at least mark-one-eyeball all the tests it's generating and tell it when it's being extra dumb.
But yeah I don't mess with wetlands.
I often try to go cash pay, since in many cases at this point it's actually cheaper, absurdly enough, and get told that I can't even get an appointment that way. I actually got kicked off primary care at a regional (fairly large) practice because they couldn't take my insurance, would not bill out of network, didn't service uninsured people (!!), and would not take cash, credit, barter or trade.