Viewing profile — xKingfisher

Even worse he changed his name from Carnagey, presumably to deliberately cause confusion.

How does it seem that Radley is talking past Gary? All discussion of the 'Misrepresentations' article is responsive to Gary's mention of it in the original article. And at no point…

> Coding for others is not art. It absolutely is, and I think it's what separates good from bad and junior from senior devs. Most devs can produce an artifact that more or less wor…

I think a distinction can be made between bad taste and different tastes. One of the greatest developers I've worked with, who I learned a lot from and respect immensely, has extre…

It's a "rain shadow"[0] The predominant wind is from the east, and the air cools aid forms rainclouds as it tries to rise over the mountains in the center of the island. Then warms…

I've had the opposite experience recently. Going from downtown Los Angeles to Santa Monica is $30s for a Waymo and runs up to $50s for Uber/Lyft (sometimes). Otherwise, they tend t…

We have common carrier laws to cover cases like Comcast. Which Section 230 explicitly says social media platforms are not. And the problem with Comcast is not necessarily that they…

The issues with the Darling 58 project had some good discussion here two weeks ago[0]. Tangentially: A distillery in Los Angeles, The Obscure, is making a rye whisky aged in Americ…

I try to avoid nits totally unrelated to the changes at hand, since on a subconscious level they may discourage people from even wanting to touch older/less loved files at all. The…

I think it's just a very confusing, hard to use correctly behavior. And according to the article, very bug prone in implementations. In the example given, the result is that both w…

There is more than just hope to rely on. Diverse Double-Compiling[0] can provably detect this class of attack. [0] https://dwheeler.com/trusting-trust/

But you can do almost all that while working at Google. And imo, the stability makes it even easier to do so. It's been my experience that Google is a super chill place to work, es…

It's mentioned in passing at the end of the "the trouble with interpreter loops" section. A traditional switch/goto loop can thrash the branch predictor. Separating into different …

An interesting application of this is massaging the branch predictor using tail calls to speed up a parser/interpreter: https://blog.reverberate.org/2021/04/21/musttail-efficient-i…

Federal prison doesn't have parole, it is a fixed 'good conduct' credit of up to 54 days per year. So she's serving a little more than 9 years minimum.

They still have a number of issues. * They're expensive (~4-8 dollars per follicle) with a single transplant being 1000-5000 follicles. Severely bald men may need multiple * There …

It's definitely a lot to process. I found these two articles really helpful when trying to understand moves: https://abseil.io/tips/55 https://abseil.io/tips/77 Though I'd also say…

The article did touch on a possible reason for the misunderstanding. If you already know from previous versions that push_back makes a copy and that C++11 added move semantics and …

And explicit constructors won't save you from this one.

Given the whole scanf/strlen thing going on, more blog posts about API pitfalls wouldn't necessarily be a bad thing. And that is basically the premise of the Abseil Tip of the week…

Maybe they're fans of why's guide to Ruby :) Though place_back still has the connotation of 'take this thing and put it over there' that emplace_back is actually the opposite of. N…

It's not bad advice. I see many code reviews that use emplace_back because it's 'faster'. Though I think the abseil article does a better job of explaining why: https://abseil.io/t…

Something like construct_back would've maybe been a little clearer. I imagine that would have it's own issues as well though.

Not to mention the very real risk of accidently invoking the wrong constructor. If you change the type of a vector, push_back is a good deal safer than emplace_back. Especially sin…