xKingfisher

I would have considered "the system" to also include password reset policies.

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 does Radley appear to endorse its contents.

> 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 works. But one that has an internal consistency others can understand and extend, one which accurately captures the problem as it exists and ways it will likely change, is much more of an art form.

A big part of that is knowing which situations are worth making a stand. Every you write code or leave feedback, your doing it for your team current and future.

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 extremely different tastes in software from me. To the point where I wouldn't say I think he has good taste.

But, his work still has a distinct style and intention. I can tell anytime I come across libraries he had a hand in. I understand what the code is doing and why is is correct, even when I disagree with it.

And I think that is what is important. When working with more junior people, I'll ask them why they did things a certain way and will generally me be with a "well, idk" of some variant of path dependence.

I think developing that intentionality as a developer is important. Which does come with some amount of aesthetic, and I think taste is a defensible metaphor.

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 to be within a few dollars.

I figured it was a combination of Google subsidizing rides and a lack of a "traffic tax".

They're a significantly better experience for 45+ minute rides.

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 will make speech decisions we don't like (an inherent part of free speech). The problem is that they're a monopoly and people don't have other options. So we should fix that problem instead of further limiting 1A rights.

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 critical exception being avoiding issues due to path dependence.

E.g while a change is "correct" is doing X poorly because of surrounding issue Y. So we should fix Y now instead of building atop it.

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 writes happened before both reads, which directly contradicts the source. There's a valid explanation for why it happens, but it's still paradoxical.

I remember at work a C++ standards committee member was giving examples of atomic and how to use them safely with different memory models, when someone pointed out his toy example for relaxed order was wrong. It took 5 people debating for a week to figure out what a safe/correct behavior would be. For a 10 line sample class.

As times your second question, the article recommends Hans Boehm's proposal to add a no-op conditional branch after the read. I guess it forces the load to be resolved and enforces a sequenced-before behavior on the individual threads. So at least one read must resolve before one write in the example.

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, especially when you take advantage of the fact that you're just one cog among many.

You get 5 weeks pto plus 4 weeks work from anywhere. This year alone I'm going to the Arctic, Antarctica, and the Carribean. Including a 40 day stretch without internet. I couldn't imagine doing the latter in a startup.

And all the while getting paid and having the comfort to make plans knowing that I'll (probably) continue to do so in the future.