Blog Posts: Rust

In my previous post, I shared some of my thoughts on the CodeCrafters website and the coding challenges it offers. In particular, I had completed the HTTP server challenge in Rust and Claude Code challenge beta (notably, the number of available stages, and the feature set of the “completed” code, are quite limited) in Python and was working on the Interpreter challenge in Rust. I have since completed the Interpreter challenge, and decided to share some more thoughts on the experience.

CodeCrafters is a site where one can complete a number of programming challenges. Challenges include: Build your own HTTP server Build your own Interpreter Build your own Shell Build your own Claude Code (still in beta) Each challenge is broken into a number of steps, with an extensive test suite triggered by the command codecrafters submit which: Pushes your submission to a Git repo on the CodeCrafters server Runs the tests for the given step Reports results back to the user in the terminal Supposedly, this is made possible by Git’s post-receive hook, which runs the test suite and reports the results back to the user via Git’s side-channel communication capabilities (as well as updating the user status in Codecrafter’s database if the step was cleared sucessfully).