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’s Termdebug

vim and the quickfix list: jump to a location, search and replace in multiple files, and other shenanigans: One of the best blog post about the underrated Quickfix list that I use all the time. #vim

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 Lisp Scripts

Engineering Design Optimization, by Joaquim R. R. A. Martins and Andrew Ning.

Higher-order list operations, or how to write recursive functions using pattern matching, and more. #racket #haskell

/me is listening to “Odds Bullets and Blades Pt II” by Soft Machine

TIL about panache, which looks like a quite capable LSP and linter for markdown (also quarto and Rmarkdown).

Randomly walking in Paris

From Buffon’s Needle to Buffon’s Noodle. I can’t help but enjoy this sort of post, which features such lovely interactive illustrations.