dmesg --follow
[ 68692020.000 ] posts.x: Full talk on building a structured query engine for agent context, from schema discovery to self-correcting queries:  |   [ 68692020.000 ] posts.x: When Claude starts a task with no context attached, it behaves like a brand new employee: grepping through the codebase, guessing at what matters…  |   [ 68673720.000 ] posts.x: @davidsenra you will love this!  |   [ 68673600.000 ] posts.x: https://t.co/vhJifvV8y9  |   [ 68673600.000 ] posts.x: This Jay-Z documentary, In 8, is exceptional! Nearly 6 hours of intimate conversation between @sc and the brilliant @RickRubin. It’s rare to get such…  |   [ 68662260.000 ] posts.x: Full talk on turning re-prompted fixes into linters, including the OpenAPI drift fix and the skill-writing whack-a-mole:  |   [ 68662260.000 ] posts.x: Re-prompting an agent to fix the same sloppy pattern over and over isn't a workflow, it's a sign the rule should live in code, not in your head…  |   [ 68650020.000 ] posts.x: ↻ @willcb: me: kinda fucked up how many people are offloading their whole lives to muse or instinct or grokbot or whatever claude: yeah  |   [ 68650020.000 ] posts.x: ↻ @iamdevloper: signs you've become the senior dev: you're the only one who understands the deploy script you're the only one who remembe…  |   [ 68649720.000 ] posts.x: Gooooooooood morning! Brazil Oberon Cerrado. Roasted 110 seconds past first crack. Milk chocolate and almond.  |   [ 68647800.000 ] posts.x: @Saanvi_dhillon “Git expert” is a weird flex, though, isn’t it?  |   [ 68610720.000 ] posts.x: @sujee_dev @dkundel @aiDotEngineer Thanks mate!  |   [ 68600580.000 ] posts.x: Full talk on the Codex app server protocol and what you can build on top of the Codex harness:  |   [ 68600580.000 ] posts.x: A lot of engineers assume building their own agent interface means writing their own agent harness from scratch. @dkundel, Developer Experience Lead…  |  
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