jwolfe

They said casual, not causal.

For cases where 4.5 already met the bar, I would expect 50% preference each way. This makes it kind of hard to make any sense of that number, without a bunch more details.

If you use the standard typescript linter, it will fail if you pass a Promise to an if statement.

https://typescript-eslint.io/rules/no-misused-promises/

If the functions are still calling I/O methods directly rather than the I/O being externally driven, I don't think that qualifies as sans-io, based on my previous exposure / based on your second link:

> For byte-stream based protocols, the protocol implementation can use a single input buffer and a single output buffer. For input (that is, receiving data from the network), the calling code is responsible for delivering code to the implementation via a single input (often via a method called receive_bytes, or something similar). The implementation will then append these bytes to its internal byte buffer. At this point, it can choose to either eagerly process those bytes, or do so lazily at the behest of the calling code.

> When it comes to generating output, a byte-stream based protocol has two options. It can either write its bytes to an internal buffer and provide an API for extracting bytes from that buffer, as done by hyper-h2, or it can return bytes directly when the calling code triggers events (more on this later), as done by h11. The distinction between these two choices is not enormously important, as one can easily be transformed into the other, but using an internal byte buffer is recommended if it is possible that the act of receiving input bytes can cause output bytes to be produced: that is, if the protocol implementation sometimes automatically responds to the peer without user input.

That's already noted at the end:

> The idea behind static_assert is great. You run a check that has no impact on the performance of the software, and may even help it. It is cheap and it can catch nasty bugs. It is not new to C, but adopting the C++ syntax is a good idea.

Over a million people die annually from traffic accidents.

It's not heavy handed. It's responding to what sells in the market, and big phones are consistently what most people buy when they have the option of both.

> Edit: GPT4 fails If I remove the sentence between (()).

If you remove that sentence, nothing indicates that you can see you picked the door with the car behind it. You could maybe infer that a rational contestant would do so, but that's not a given ...

You're misreading that source. It's the separate npm packages that are deprecated, not the module imports.

If you're confident about your proof checker being correct, then why would you not be confident about the validity of a proof that your proof checker says is correct?

Right, but then your AI is frozen in time and/or requires much more manual curation of its inputs. What about for new programming languages, libraries, and APIs that are created after 2022? What about generating images of new technologies that are invented, or new landmarks established?

I think you're specifically referring to plastic waste in the ocean. This number is not at all accurate in terms of total plastic waste (including landfills, etc.).

The rest of the sentence that you left off in your quote is saying that blocking POST requests is worse than overzealous. You are in agreement with them.

Maybe give this a scan, to understand the impact it had had on AWS as of 2015: https://lamport.azurewebsites.net/tla/amazon-excerpt.html

> Obamacare made a great effort to decouple health care insurance and benefits from the employer

Did it? There was lots of talk at the time about how you get to keep your private plan. And the actual text of the ACA mandated that large employers offer health insurance, which was not the case before the ACA.

What provisions in the ACA made great efforts to decouple them? i.e., which provisions incentivized individuals to not be on employer plans, or employers not to offer them?

The issue is not exposure to hatemail.

The issue is exposure to child pornography and videos of people literally dying, all day every day. These are not comparable to the pain of being banned, and therapy is nowhere near sufficient.

https://www.theverge.com/2019/2/25/18229714/cognizant-facebo...

It should be noted that this is self-promotion.

This metaphor also fails, in the existing regulatory framework. If you own a printing press and print something, you are liable for its contents. Twitter, under Section 230 of the Communications Decency Act, is not liable for content that its users post.

> If a corporation wants to operate a public space, like a square with a fountain outside an office building, you generally have to follow the law on what speech is allowed in that space. If your square is in the US, you have to allow Nazis to protest, but if it's in Germany, you probably have a duty to call the police on the Nazis to stop them.

This is not correct. [0]

> Private property owners can set rules for speech on their property. The government may not restrict your speech if it is taking place on your own property or with the consent of the property owner.

[0] https://www.aclu.org/know-your-rights/protesters-rights

I'm not pro-gun and do not own any, but if I had to fire a gun in that instance I sure would prefer my ears to be able to tell me if there were someone else in another room shortly after the fact.

> The solution is to build more, and the success of Vienna does not come from public intervention but from the added supply. Tokyo is another city with famously cheap housing, and the secret is that they make it easy to build.

The other two secrets are tiny apartments (200-400 sqft), and an incredibly reliable public transportation system. Tokyo has a massive sprawl -- people can and do live far from their work. The average one-way commute time in the Tokyo metro area is almost an hour.

And requires centralized exchanges subject to Know Your Customer regulations to get your money out as fiat.

I suspect it's pretty hard to make the case that the average Rust program is harder to write than the equivalent C program. I suspect it is quite the opposite. The language provides so many tools that didn't exist in the age of C -- high level concepts like Iterators, destructuring match statements, deriving debug printing for free, etc.

But both of our opinions are just opinions.

The news frequently talks about short staff at hospitals, in my own observations.

Is there any evidence supporting vaccine requirements being a larger source of nurse attrition than burnout?

> Meritocracy does exist and does work, except where it is undermined (i.e. "Equity", or assigning merit based on immutable physical traits like race and gender).

Allowing inheritance from one generation to another is an immediate disqualifier for meritocracy as well. As is the existence of private schooling bought with money.

Do you care about being around social justice or bringing about social justice? If the former, sure, move to a blue area. If the latter, wouldn't moving to a purple area be more impactful?

It seems in context that they're saying that you may or may not consider the fact that you worked hard and then were heartily rewarded to mean that you deserved the result. Especially in the context of many many other people working just as hard and not getting the same result.

Couldn't it be as simple as a list of (color, x, y, z) (base64 encoded) in the fragment? URL fragments can get really long.

Not sure what you'd need a look up key for.

Not knowing about the ability of it to do that is not evidence that the ability doesn't exist. You were already trusting them not to do this before, since they had full access to the texts and images as the developer of the app.

The development of systems that can recognize these kinds of images predates this and you likely have been previously aware of them already existing and the ease of deployment of them.

Trust of Apple is already all that stood between them being abused and them not being abused.

I don't really understand what argument is being made here.

Is a big concurrent sharded DB necessarily a "harder problem" when it's provided to you by another team at the company to use?

The skills you need just seem different to me.

In the large case, the more important skills are going to be the higher level reasoning of what is a good shard size, how do we avoid hotspotting, what is an appropriate way to partition for the set of queries we want to run. None of those really help you solve the smaller problem. You're also going to likely be relying on infrastructure-provided solutions like automatic backups.

In the small case, you're going to need to worry about things like those backups. Then there's the skill mentioned in the interview -- it seems like this person had never had to actually think through how much space N rows of a particular schema were going to take up in memory, or how much order of magnitude QPS you can get out of (e.g.) a MySQL server. You're also going to be optimizing to different peculiarities of what is fast to do on this different database technology, which sometimes does not translate directly. In a smaller company (more so in older days, but still in some places) you may also need to deal with the operational challenges of buying and installing a bigger box if it's called for.