I don't see any reason why we shouldn't make this transitive. working professionals track the literature. if there were a standard way to publish a "I think this paper is interesting" signal, then we could roll that all up. there are certainly practitioners that I really do trust to be in the game for the right reasons, if they think a paper represents a contribution, then that's a strong signal for me.

this reference does talk about those stats, but doesn't link in any way to adverse affects of attempting to bring down deaths.

this is not at all restricted to your case. try 'distributed system engineer' or even 'software engineer'. for the latter, one is an engineer of software, and the other is one that engineers with software. both perfectly valid jobs. it doesn't help that the interviews for the latter adopt the questions and expectations of the former, even though they are different jobs.

its entirely possible to go through the software engineer hiring pipeline, and end up in a situation where the organization and the new employee have a fundamental disagreement about the slate of work.

somehow in the giant waterfall of money, our ability to even talk meaningfully about our work to each other got lost

you're right. there are a couple explanations that might have some merit looking at it from the device perspective. one is the the underlying block size is really large, so that looks like a very large cache line that a sequential scan will always hit. its also very likely that there are prefetchers running to try and hide the latency.

how many scheme compilers do you think have been written?

Hundreds, this is one of the most famous functional programming exercises (mostly thanks to SICP). Just check https://github.com/search?q=scheme%20compiler&type=repositor... (858 results on github)

Probably many SICP or "Write Yourself A Scheme" readers have pushed basic scheme compilers to GH.

if you're trying to write rust without thinking about the abstractions then yeah, its probably non-terminal. I would strongly suggest making the broad strokes yourself and letting it fill the details.

I have fixed the target data structures and also make Claude compare the generated code against a python reference via PBT. However, the vibe-coded code generator stumbles upon a missed clone/copy case every now and then. This is where I am less certain that it converges.

I don't know why we're getting mired in the details here. The administration certainly isn't. We all work for trump now. Lawyers, journalists, universities, tech companies, state, local and foreign governments. Anything trump or one of his designated people wants, you need to do. If you start sputtering about your agency or your rights or your sovereignty, then expect as much shit thrown at you as the trump organization can muster. That's it, there is no legal justification. There are no fine points to argue. Obey or be punished.

The point is that someone claimed the law was changed, and then linked to something that didn't support the claim.

Yes, Trump is ignoring the law, but you have to be aware that he is crossing the line rather than gas lighting that there wasn't a line at all.

buts it not a national emergency. its not a time of war. and there is a different between demanding to be customer, and demanding that you change your products because they would like them to be a different way. that is actual conscription.

for many decades, the DoD has used a carrot to get what they want. this is a stick.

unlike the old hpc, where we only burned hundreds of millions for machines that were 80% efficient to get a 5 year lead, we are burning hundreds of billions on machines that are 30% efficient to get a 1 year lead.

that solves the pollution problem, but it doesn't pin cache lines. it also doesn't cover the case that ppc does where you want to assert a line is valid without actually fetching.