Posts
He Went to the Slop Side
LLM Reviews in cargo-crev
I don't want your PRs anymore
Reviewing my Framework 13 Laptops: the old vs new
BubbleWrap your dev env and agents
Personal AI usage disclosure
Setting up own Radicle Seed Node with NixOS
Helix file picker with lf
Cool Fish Shell abbreviations
Remap Caps Lock to Esc and some
Pretty selection sort in Rust
You can't just avoid complexity
Nix users, you can fearlessly start using Rust scripts already
Did some CLI/terminal self-care over the weekend
Embedding git version hash in a binary in a Nix friendly way
Migrating my blog from write.as
git alias to make a single commit reverting to previous commit
If you ever need to make a PR that just reverts the state of a branch to a certain point, you might find this useful:
Be careful what you measure because you will optimize it
Humans are very competitive. If you give them a number to rate themselves with, they will try to increase it.
If you find an Open Source project, and it's not very optimized on a certain metric you care about, to make it better, you have to do only one thing: write a benchmark for it. Ideally showing this project is worse in a given metric compared to some other similar projects. You're almost guaranteed that in a short time there will be improvements.
Most people must be familiar with the quote:
“Measurement is the first step that leads to control and eventually to improvement. If you can’t measure something, you can’t understand it. If you can’t understand it, you can’t control it. If you can’t control it, you can’t improve it.”
― H. James Harrington
It's an important insight and people internalized and wish to apply it... even where it can't be.