This is an interesting de-obfuscation tool that Trail of Bits has built. I'd never come across this technique of hiding logical/arithmetic operations so it was interesting to learn about it and how they've attempted to de-obfuscate it.

> Using these more sophisticated data structures, g++ is able to compute the prime numbers below 10000 in only 8 seconds, using a modest 3.1 GiB of memory.

Finally, I can get some primes on my laptop!

This is a concerning read, I'm not quite sure what the driving motivation is for Artemis, but the following answered at least part of my question -

> That context is a moon program that has spent close to $100 billion and 25 years with nothing to show for itself, at an agency that has just experienced mass firings and been through a near-death experience with its science budget

I understand why NASA might be a little antsy but 100B over 25 years doesn't seem like a lot for America for a long horizon project.

It's 100b just to begin - the full bill would be multiples of that.

And there are options now.

They said they're replacing 15 years of Nginx+Lua, that's a testament to how good it can be.

It reminds me of the mercury delay lines - https://en.wikipedia.org/wiki/Delay-line_memory

"I have one memory system remaining. Delay-line."

https://vgel.me/fiction/gyre/

very cool story

This is an interesting approach to problem solving that I'm surprised an LLM would help with. There is also a followup [0] releasing this tool as a Claude plugin (I haven't tried it myself). I'm much less interested in the application (DeFi) than in the possibility that we could use tools like this to eliminate common classes of bugs like dimensionality errors.

[0] - https://blog.trailofbits.com/2026/03/25/try-our-new-dimensio...

I couldn't quite follow the logic in this article, though some comments on here have clarified what it seems Drew means here. To be honest, this spiralling logic reminds me of my thought processes when I was at my most depressed

I had added a file to (I think) .git/info/exclude for .... reasons, which worked well until I couldn't find that file with rg. It's still my default grep though.

I remember listening to a podcast (possibly complex systems?) that said the best way to find what kinds of frauds are out there is by looking at what known fraudsters are up to.

[0] It might have been this one, but I can't find it in the transcript https://www.complexsystemspodcast.com/episodes/fraud-as-infr...

To be honest I prefer this type of communication over the I-can't-believe-it's-not-layoffs that my previous employer was doing. At least it's honest that it is a decision they've made.