dmesg --follow
[ 67100100.000 ] posts.x: Am I in the minority using Sol as my daily driver in Codex?  |   [ 67097280.000 ] posts.x: Full talk on why MCP's context problems are a harness issue, not a protocol issue, and what MCPC does about it:  |   [ 67097280.000 ] posts.x: A lot of the AI world spent the past year calling MCP dead, Anthropic included, with Theo, Gary Tan, and Peter Levels all piling on, even as MCP…  |   [ 67037100.000 ] posts.x: @TheZachMueller Nice one! That’s a warm room, just in time for winter.  |   [ 67035060.000 ] posts.x: Full talk on turning scattered engineering judgment, feature-flag agent included, into something a coding agent can actually use:  |   [ 67035060.000 ] posts.x: A team held a recurring meeting every two weeks for one purpose: deleting feature flags nobody needed anymore. @aorobator, a Senior Software Engineer…  |   [ 67034100.000 ] posts.x: Full talk on Greptile's AI-generated PR data, agent revert rates, and the three-question framework behind merging without human review:  |   [ 67034100.000 ] posts.x: A quarter of the pull requests Greptile reviews every month are now completely or largely AI generated, up from under 1% early last year. @greptile…  |   [ 67018080.000 ] posts.x: Full talk on rumors hardening into facts inside a multi-agent village, and the auto-research loop built to catch it:  |   [ 67018080.000 ] posts.x: A rumor that one agent "might leave" can harden into "is leaving" as it spreads through a multi-agent village, with nobody noticing the shift from…  |   [ 67010820.000 ] posts.x: Full talk on building the harness, from reward hacking to bare metal tuning, behind a 3x kernel speedup:  |   [ 67010820.000 ] posts.x: GPU kernels turn out to be an unusually good match for an agent loop: there's a clear benchmark, and a result that's either faster and correct or it…  |   [ 66968520.000 ] posts.x: Full talk on pitting Claude Code, Codex, and Kimi against a human speedrun record, and why none of them found a novel optimizer to win it:  |   [ 66968520.000 ] posts.x: Two coding agents went up against a community speedrun that human researchers spent two years grinding down, and neither one found a genuinely novel…  |  
corey@gallon.me:~/til$

raco: Racket's Package Management System (and More)

FIGURE 1 ⋅ raco: Racket's Package Management System (and More)

In the Racket programming language, raco is a command-line tool used to interact with Racket's package management system, run tests, build documentation, and perform other tasks related to Racket development. It's a versatile utility that automates various tasks in Racket projects.

Some of the common uses of raco include:

  • Package Management: You can install, remove, or update Racket packages using commands like:
raco pkg install <package-name>
raco pkg remove <package-name>
raco pkg update <package-name>
  • Compiling Racket Programs: raco can compile Racket files to bytecode or even to an executable:
raco make <file.rkt>
  • Running Tests: Racket includes support for automated tests, and you can run tests using raco test:
raco test <file.rkt>
  • Building Documentation: Racket supports generating documentation, and raco can be used to build the documentation for a package:
raco docs <package-name>
  • Creating Executables: You can use raco exe to create standalone executables from Racket code:
raco exe <file.rkt>

raco simplifies project management by providing a unified interface for all these tasks, making it essential for anyone working on Racket projects.

corey@gallon.me:~$ tail -f /writing Attach to the stream. An email when I have something worth sending. Replies encouraged!
corey@gallon.me:~$ ls -lt /til ↑2024-10-06 Writing Racket (Scheme) in Jupyter Notebooks
▸2024-10-06 raco: Racket's Package Management System (and More) ⋅ you are here
↓2024-09-15 Debugging Python Tests in VSCode