dmesg --follow
[ 68173020.000 ] posts.x: Full talk on the six ways to actually work with Codex, from app shots to automations and the open source app server:  |   [ 68173020.000 ] posts.x: A handful of examples set the bar for what people are building with Codex: a single session with nearly 300 sub-agents, a synth plugin for Ableton…  |   [ 68157360.000 ] posts.x: Full workshop on turning feature requests into job statements and prioritizing them with the Kano model:  |   [ 68157360.000 ] posts.x: When AI agents level the implementation playing field, building the right thing becomes the actual differentiator. That's the thesis @kentcdodds, a…  |   [ 68151420.000 ] posts.x: I updated my article on Codex context windows. The old trick works again, on GPT-5.6 this time: set model_context_window in a profile and you get…  |   [ 68144100.000 ] posts.x: @GeoffreyHuntley  |   [ 68144100.000 ] posts.x: @varun_pant_  |   [ 68141880.000 ] posts.x: Full workshop on the sandbox failure modes E2B built this CTF around, from runaway processes to orphan cleanup to sandbox lifecycle management:  |   [ 68141880.000 ] posts.x: Most sandbox bugs don't show up when you're running one of them. They show up once you're running thousands. @badphilosopher, an AI engineer at E2B…  |   [ 68138220.000 ] posts.x: This flash memory shortage is no joke! I paid $180 for this 2TB SSD in December 2024. It's now $570. Usually drive prices *decrease* over a similar…  |   [ 68133780.000 ] posts.x: Full workshop on building the right thing before building it right, including the mom test questions and Don Norman's take on user error:  |   [ 68133780.000 ] posts.x: Implementation used to be the hard part of software engineering. Now agents handle that fast, so the differentiator becomes deciding what's worth…  |   [ 68093280.000 ] posts.x: Full workshop on building an LLM judge from scratch, the biases that make it lie, and the Instagram chatbot incident that shows why it matters:  |   [ 68093280.000 ] posts.x: An Instagram support bot once let attackers past two-factor authentication with nothing more than a VPN and a polite request, and 20,225 accounts got…  |  
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