> ## Content Index
> Fetch the complete content index at: https://blog.matthewbrunelle.com/llms.txt
> Use this file to discover other available public pages before exploring further.

# Notes on using CodeCrafters on NixOS
- URL: https://blog.matthewbrunelle.com/notes-on-using-codecrafters-on-nixos/
- Published: 2026-11-19T17:06:08.000Z
- Updated: 2026-11-19T17:06:08.000Z
- Description: I'm trying out CodeCrafters to get hands on programming time, but as usually there are a couple of quirks to work around on NixOS.
- Author: Matthew Brunelle
- Tags: NixOS

#### On this page

As I mentioned in my post on [practicing Rust](https://blog.matthewbrunelle.com/finally-actually-hopefully-learning-rust/), I'm a big fan of Anders Ericsson's concept of deliberate practice:

- Setting aside time to practice specific skills with focused attention.
- Not so hard that you can't make progress.
- Not so easy that you don't stretch and learn anything (mindless repetition).
- Getting feedback as you go.

I'm especially trying to do this now without any form of AI assistance.

For a couple of months now I've been trying out CodeCrafters, which provides programming-in-the-medium-scale style projects. I'll note this post is not a review. Rather, I've run into gotchas with running the projects on NixOS and wanted to share notes.

---

## Setting up a Python devshell

Wait, Python. I thought I was learning Rust? If I do a project for the first time in Rust, I'm both figuring out how to solve the project and learning the idiomatic way to write the project in Rust.

Python is what I work in day-to-day, so I've started doing projects first in Python. That way I'm only thinking about how to do the implementation. Then I go back and redo the project in Rust with a focus on learning the language. Otherwise, I find myself in that spin-the-wheels territory of difficulty. So Python it is.

There are several ways you could set up a devshell. I'm using [the-nix-way template](https://github.com/the-nix-way/dev-templates?ref=blog.matthewbrunelle.com) which is a little heavy handed, but for practice work I want to spend my focus on the problem, rather than tooling setup.

To generate the devshell you just need to call `flake init` with the repo and the `python` tag:

`nix flake init --template "https://flakehub.com/f/the-nix-way/dev-templates/*#python"`

Then run `direnv allow` to load the devshell automatically when you change directory. I also added these packages:

- pkgs.codecrafters-cli
- pkgs.ruff
- pkgs.ty
- pkgs.uv

The instructions on the CodeCrafters site have you curl a script to install the CLI. We've always known this was a bad practice and the eMudhra certificate compromise made fclear why. Thankfully the CLI is available in nixpkgs.

I also added ruff, ty and uv, but feel free to pick your flavor of Python tooling.

---

## Make sure to git ignore the .direnv directory

Each project section requires passing a set of remote automated tests. When I went to run my first test, I hit this failure:

```
[build] Starting build...
[build] If you don't see logs for 60s+, please contact us at hello@codecrafters.io
[build] Step 1 complete.
[build] Step 2 complete.
[build] Step 3 complete.
[build] Step 4 complete.
[build] Step 5 complete.
[build] Step 6 complete.
[build] Step 7 complete.
[build] > [auth] Started verifying token authority from the client for registry-1.docker.io
[build] > [auth] Completed verifying token authority from the client for registry-1.docker.io after 0.029s
[build] Step 8 complete.
[build] Step 9 complete.
[build] Step 10 complete.
[build] Step 11 complete.
[build] Step 12 complete.
[build] Step 13 complete.
[build] Error: failed to calculate checksum of ref kxhqe7styo2ze7w6t4x9x1r79::vnpdjkei85yyrpecgdo099uku: "/nix/store/5h3znhm5wqj8qsf9bf1apfl82cyfadxp-source": not found.
[build] Build failed. Check the logs above for the reason.
[build] If you think this is a CodeCrafters error, please contact us at hello@codecrafters.io.

```

Turns out CodeCrafters will `git add` all files in the project folder that are not explicitly git ignored. I am not particularly a fan of this, especially since you are not warned.

Regardless, the CLI was adding my .direnv folder, which references the Nix store, so I had to add `.direnv` to the `.gitignore` file.

---

Those are the main road bumps I've run into so far. I'll update this post with more as I find them.

On the whole, the practice projects they have seem pretty okay, though some are better than others. Also, language coverage is not consistent across projects. For example, many do not offer Crystal as an option and the one that does is out of date.

Also, CodeCrafters is *extremely expensive*. They almost [went under](https://codecrafters.io/blog/pausing-new-challenges?ref=blog.matthewbrunelle.com) back in May, until they got a new CEO in September. Weirdly, I can't find the CEO announcement online anywhere, but in an email they said:

> In late May, Paul and I shared that we were pausing development of new challenges. Following the news, our inboxes were filled with an incredible amount of love from you, and also expressions of sadness - which made it really difficult to not try harder to keep the mission going.

So at least for now I can keep practicing until my subscription ends.