Micro posting in May
2026-05-03: The MacBook Pro G4 from 2005 had 6 ports on the right side. Modern MacBook Prohave two Thunderbolt 3/4 with USB-C slots + one SD-Card reader.
2026-05-05: /me is listening to “Step Into The Gray” by Stuart A. Staples
2026-05-05:
Apple used to be a one-book religion. Apple’s Human Interface Guidelines used> to be cited by every User Interface course over the world. Xerox PARC and> Apple were the two institutions that studied what it means to have a good> human interface. Fast forward a few decades, and Apple is doing the best worst> it can to break all the guidelines and consistency it was known for. — Why TUIs are back
2026-05-05: If you use IPython as your REPL of choice when editing Python files in Neovim, and you also happen to use uv to manage your project, the following keymap might be useful:
nnoremap <buffer> <silent> <leader>! :sp term://uv run --offline --with ipython ipython --no-banner<cr><C-w><C-w>
The first time it will install all IPython dependencies, but it will run
smoothly on next runs. The advantage is that uv’s IPython is aware of your
project dependencies, contrary to IPython installed system-wide (e.g., via
Homebrew or uv tool). #vim
2026-05-15: I didn’t know there were so many flavors ofVi… #vim
2026-05-15: Nice summary of rysnc: Farewell to scp.
2026-05-15: Think Linear Algebra. #python
2026-05-15: You opened this page. It already knows the following.
2026-05-16:
Randomly walking in Paris
2026-05-16:
Beyond pure operations, IRC was also a social space with its own culture, rituals, and hierarchy. You proved yourself by sharing information, by having access to tools before others did, by being present when something interesting happened. The channels were chaotic, frequently toxic, and also a brutal apprenticeship in network security for anyone who could not afford a conference ticket. Many people who are now respected professionals in DFIR, threat intelligence, and red teaming learned the fundamentals there. — Back in my day we hacked with style: a sentimental tour of late 1990s and early 2000s tools
2026-05-16: Category Theory for Tiny ML in Rust: A practical bridge between compositional mathematics, Rust types, and tiny machine-learning systems. #rust
2026-05-16: From Buffon’s Needle to Buffon’s Noodle. I can’t help but enjoy this sort of post, which features such lovely interactive illustrations.
2026-05-16: Six SQL patterns I use to catch transaction fraud: SQL is de facto a language for data wrangling.
2026-05-16: The Emacsification of Software. I settled upon Typora as my native reader, although I process all my Mardown file with Neovim.
2026-05-17: /me is listening to “Odds Bullets and Blades Pt II” by Soft Machine
2026-05-17: TIL about panache, which looks like a quitecapable LSP and linterfor markdown (also quarto and Rmarkdown).
2026-05-18:
I’m not against writing code with debuggability in mind, but implicit returns are an idiom in Rust. It feels so unnecessary to reduce the idiomatical adherence of the code due to a DAP gap, especially when the debugger on the other side of DAP supports logging return values. Just don’t make me do this. — Debugging Rust with Vim’sTermdebug
Roswell is advertised as a solution, but it’s possibly the most un-Lispy tool in the ecosystem. It doesn’t download dependencies, or help you build them.— Deploying Common LispScripts
2026-05-18: Engineering DesignOptimization, by JoaquimR. R. A. Martins and Andrew Ning.
2026-05-18: Higher-order listoperations, orhow to write recursive functions using pattern matching, and more. #racket``#haskell
2026-05-18: vim and the quickfix list: jump to a location, search and replace in multiplefiles, and othershenanigans:One of the best blog post about the underrated Quickfix list that I use all thetime. #vim
2026-05-19:
The old tram tracks of Paris (10 meters from the new tracks).
2026-05-20: /me is listening to “They Say in Love” by The Tempers
2026-05-26:
2026-05-26:
Over the past few years, it seems like the rate at which new CLI tools are being written has picked back up again, accelerating after seeing relatively little activity between ~1995 and ~2015. — The Modern CLIRenaissance
the key point is that matrix transpose serves as a prime example of the problem which appears trivial but nevertheless requires tremendous effort to be solved efficiently for CPU. Root causes of this unpleasant surprise can be traced to high memory latency and limited parallelization capabilities of CPUs. Neither of these issues is going to be alleviated in the future. — Whatit takes to transpose a matrix