RocksDB development finds a CPU bug This is the story of how a RocksDB unit test I added four years ago, a mini-stress test you might call it, revealed a novel hardware bug in a newer CPU. It w...

Generating random number is really hard. Sometimes there is a bug in the CPU that you’re using.
rocksdb.org/blog/2026/02...

"The absolute beginners guide to databasemaxxing"

pthorpe92.dev/databasemaxx...

Monday the 16ths, on the other hand, make you lose sleep on Sunday evenings. 😰

The “agressive leftism” accusations on X, have been widely exaggerated.

Alright. Americans and their confusing colloquial use of the term “liberal”.

Liberalism is too broad of a term. Hard for me to not connect the neoliberal ideas of Tatcher and Reagan to the conditions that helped fascism rise again.

80-character line limit so you can review Claude Code output on your VT100 terminal and your phone.

I opened YouTube this week and it recommended the web scale MongoDB video. Metadata says “15 years ago” and that made me feel very old.

Até eu que me interesso por finanças e investimentos acho insuportável.

In Arrow C++, we have “length” of arrays for the “count” and buffers have “size” in bytes. But things get confusing when STL code is mixed because vector::size() is the length/count and not the “size” in bytes.

t.co/ZGkA8xvy8R

Using Cap’n Proto in Rust to get zero-copy deserialization, but Codex insists on writing de/serialization functions that build a struct full of heap-allocated strings. Because that’s what dominates the training set of model and programmers everywhere.

You might not like it, but I treat the computers I have at home as pets, not cattle.

The year of Linux on the desktop because Windows and macOS window managers are terrible if you're supposed to loop through all the AI agents you're managing at work.

Google Meet: "no one is here" before you join the meeting but only because it hasn't really loaded the response that lists who is in the meeting.

This database solution looks very dystopian

Don't put the burden on yourself to fix other people's code. Use the AI tools to write exactly the code you want, but more efficiently.

bsky.app/profile/feli...

Good time to be CLI maxxing:
- @neovim.io
- tmux
- smug (to start tmux sessions from YAML files)
- git worktrees (multiple repo checkouts for parallel agents)
- dotfiles in a git repo synced across macOS and Linux machines

Open-source can't dispense with code review, but I predict some companies will stop code review altogether and more aggressively cut people who submit slop to production.

In open-source, the idea that you're judged by your code is also not going to scale. Some kind of reputation system will be necessary for contributors to earn the right of having their code reviewed.

In this new world, by the time a PR is opened, the author should have already reviewed the coding agent’s work.

Code review, as we know it, is not going to scale. You can’t get paid to ask an agent for code, open a PR and let the review and refinements be someone’s problem.

that's why "most AI projects are failing" is not indicative of lack of potential

The hidden emotional labour of not judging PR authors' competence because of the LLM-generated slop being submitted for review.

Yes. If you're single-threaded you *CAN* mutate through an &.

A method that takes a lock and performs some mutation would be non-const in C++. But if you were to declare it as `&mut self` in Rust, you would not be able to have concurrent callers. The whole point of having a Mutex in the first place!

&mut T means "you cannot have other aliases".

This contrasts with C++ const where aliases are all over the place and const only exists to help you be suspicious about side-effects.

In Rust, a &T is not an immutable reference in the common Functional Programming sense. func(&self) is free to mutate atomics or values wrapped in Mutex through self because any other call through an alias to self is going to synchronize the mutations. &T means "you can have other aliases".

I have multiple of these

O "bom gosto" é, no final das contas, definido como aquilo que o pobre ainda não tem acesso. A partir do memento que o pobre tem acesso, para de ser bom gosto.

I had a professor in CS school that told us "if you worry about hackers, you won't get anything done" when the subject of SQL injection came up.

The 2026 version of that is: if you don't give your 1Password to Claude you won't get anything done.