jwolfe

If bash placed the current directory in your PATH by default, then yes.

You're in luck: https://github.com/apple/foundationdb/blob/main/design/corou...

They're referring to Enterprise customers, though should have been clear about it. Enterprise plans on Claude for example no longer include any baseline tokens. It's 100% usage based pricing.

That's not a very good tldr. The answer claimed in the paper is that the combination of the two is better than either alone.

Fortunately the economics of infinitely copyable software aren't going anywhere. If there is actually a sizable market, it can be served with relatively little cost, compared to hand-producing physical goods. I am not fully convinced there will be such a market, though.

Your work laptop documents are not private personal notes.

This is also partially why I do not log in to work accounts on personal devices or personal accounts on work devices.

You commonly receive very close proxies for diagnoses through MyChart already when results come back from the lab.

If it's something like "Refactored the apartment list service improving P99 Latency from 2s to 180ms", it definitely boosts the resumé in my mind. A good engineer would be measuring their impact and likely have numbers like that off the top of their head.

But if it's like "Increased revenue by $18.7M by reducing time-to-first-interaction latency from 2.3s to 117ms, increasing conversion by 47% and LTV by 28%," with the same fidelity on each bullet, I'm very skeptical.

Do you mind explaining why? The former doesn't indicate caring about business impact whatsoever (is this service in the critical path of any online process? Who knows!) while the latter does.

The comments on the article include other people replicating all or parts of the finding. I'm also pretty confident Kelsey Piper wouldn't fail to disable memory while simultaneously talking about how Claude incognito mode is insufficient to prevent the app from handing it your name.

Pre commit hooks exist. People just don't like being prevented from committing for reasons such as this.

This is a user preferences setting for what it's worth.

In general these agents support LSPs, which is often as much information as your IDE will give you. They are also not required to output syntactically correct code token by token when running agentically, because the loop is:

1. code

2. syntax check / build / format / lint (details language dependent)

3. test

and they can hop between 1 and 2 however many times they want.

I don't think it's a psychologically positive self identification to see yourself merely as a gatekeeper and toll extractor rent seeker who only makes a living by withholding agency and skill from others.

That's an incredibly uncharitable reading of the parent comment. At no point in history prior to maybe this year could you argue that working in software was gatekeeping, toll extracting, or rent seeking. Being a highly skilled craftsperson creating software for those who can't or don't want to is a very psychologically positive self identification. Lamenting that the industry is moving away from highly skilled craftspeople is also perfectly valid, even if you believe that it is somehow good for society, which is yet to become clear.

This thread is about bringing these people to the US.

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...