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$

Working through SICP in Jupyter Notebooks

FIGURE 1 ⋅ Working through SICP in Jupyter Notebooks

I’m reading Structure and Interpretation of Computer Programs and want to write Racket in VSCode in Jupyter notebooks in a dialect of Scheme closest to the book. This requires this declaration at the top of each Racket file:

#lang r5rs

HOWEVER, Jupyter doesn’t like this …

Jupyter Doesn't Like This
FIGURE 2 ⋅ Jupyter Doesn't Like This

The Jupyter kernel for Racket doesn't directly support changing the language with #lang declarations in individual cells. Claude to the rescue, though … eventually … what a pain to finally get to this!

  1. We need to find our where iracket is installed.
❯ find ~/.local -name iracket.rkt
/home/captivus/.local/share/racket/8.2/pkgs/iracket/iracket.rkt
  1. Now, we edit this file (home/captivus/.local/share/racket/8.2/pkgs/iracket/iracket.rkt) as follows:
#lang racket/base

;; ============================================================
;; Enabling R5RS mode for compatibility with SICP code
(require racket/sandbox)

(define orig-current-namespace (current-namespace))
(define r5rs-namespace (make-base-namespace))
(parameterize ([current-namespace r5rs-namespace])
  (namespace-require 'r5rs))

(define (switch-to-r5rs)
  (current-namespace r5rs-namespace))

(define (switch-to-orig)
  (current-namespace orig-current-namespace))

(switch-to-r5rs)

;; The rest of the original iracket.rkt content should follow here ...
;; ============================================================
  1. Now, restart your VSCode and create a Jupyter notebook as previously described in your TIL article … and you’re up!
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 Installing Racket (Scheme) in WSL
▸2024-10-06 Working through SICP in Jupyter Notebooks ⋅ you are here
↓2024-10-06 Writing Racket (Scheme) in Jupyter Notebooks