noboilerplate: the archived script repo behind the No Boilerplate videos

What noboilerplate actually is, and who it is not for

The repository is described as "Code for my talks on the No Boilerplate channel", and the README narrows that further: it "contains old scripts for my talks on the No Boilerplate channel, up until video 43, in scripts/". The primary language is HTML, which is a hint about what those files are rather than what they produce. Nothing in the README describes a package, a binary, a service or an API.

The audience is therefore narrow. It is useful to someone who wants to see the raw text of a video script before it becomes a video, or who wants to study the writing pattern behind a channel that teaches Rust. It is not useful to someone looking for a Rust crate, a boilerplate generator, or a tool that removes repetitive code. The repository name invites that mistake, and the README does nothing to correct it.

The licence is CC0-1.0, which places the scripts in the public domain. For a script archive that is a sensible choice: it removes friction for anyone quoting or remixing the text. It also means there is no contributor licence agreement to negotiate, and no attribution requirement to satisfy.

The scripts/ directory and the three tools behind each video

The README states the production pipeline directly: "I build these using obsidian.md and presenterm: I take each slide, printscreen it, and splice it with my audio using reaper.fm." That sentence is the whole architecture. Obsidian holds the notes that become slides, presenterm renders them as terminal slides, and Reaper combines the captured frames with recorded audio.

The repository stores only one part of that chain. The scripts live in scripts/, and the top-level tree contains little else: .github/, .gitignore, CODE_OF_CONDUCT.md, CONTRIBUTION.md, LICENSE, README.md, and scripts/. There is no build script, no Makefile, no dependency manifest, and no configuration for presenterm or Obsidian checked in at the top level. If you were hoping to reproduce a video end to end from this repository alone, you cannot. You can read the words, and you can see the workflow named, but the slide themes, the presenterm invocation and the Reaper project are not part of what is published here.

That is a real limitation rather than a flaw. A script archive that also shipped someone's personal Obsidian vault would be a different, messier project. The README is honest about the boundary: it tells you which tools were used, not how they were configured.

Getting the scripts onto your machine

There is no install step, because there is nothing to install. The README points at the scripts directory in the repository, so the practical route is to open that directory on GitHub and read the files there. The README links to it as github.com/0atman/noboilerplate/tree/main/scripts.

Once you are in that directory, the listing is the step that matters. The README does not list the individual filenames or map them to video numbers, so browsing scripts/ is the only way to find the episode you want. If you are looking for a specific talk, read the filenames rather than guessing, because nothing in the repository indexes them by topic.

What you should expect to see is a set of files whose contents read like spoken narration, not like runnable code, even though the repository's primary language is reported as HTML.

If your goal is the newer material, the README is explicit that this is the wrong place: "All future videos are hosted on the Namtao.com site's main repo, and published at namtao.com/nb/." Go there instead of opening an issue here.

Where the repository stops being useful

The README's first line is a redirect, and it should be read as a boundary rather than a note. Everything after video 43 lives in github.com/NamtaoProductions/namtao-com under src/site/notes, and is published at namtao.com/nb/. A reader who opens noboilerplate expecting the current catalogue will find a truncated one.

The second limitation is the pipeline gap described above. The README names presenterm and Obsidian but does not document how they are configured, so the repository cannot be used to rebuild a video. Anyone treating it as a template for a talk-recording setup will have to reconstruct the presenterm side themselves from that project's own documentation.

A third point is maintenance. The last push to this repository was on 2026-05-24, and the README describes its contents as "old scripts". The repository is not archived, so it remains readable, but the README's own text tells you where active work went. Treat this as a fixed archive, not a project with a roadmap.

Finally, the recommended reading list in the README (the Rust Book, fasterthanli.me, Rust By Example, Rustlings, the channel's own Rust playlist, and a Discord server) is a curated set of external links. It is genuinely useful if you are learning Rust, and it has nothing to do with the repository's own files. Do not confuse the two when judging what the project offers.

What to use instead if you wanted a tool

If you arrived here looking for software that strips repetition from your codebase, this repository is not it, and the closest real alternative depends on which half of that idea you meant.

For slide-based technical talks rendered in a terminal, presenterm is the tool the README names, and it is a separate project by mfontanini. The difference in approach is direct: presenterm executes a markdown file to drive a presentation, while noboilerplate stores the prose that was spoken over the resulting slides. One is the renderer, the other is the transcript.

For note-taking and slide authoring, obsidian.md is the second tool named in the pipeline. It keeps notes as plain markdown files in a local vault, which is why the scripts in this repository are readable as text in the first place. If your interest is the writing workflow rather than the videos, Obsidian is the thing to install, and the README gives you no configuration for it.

For the Rust teaching material itself, the README's own list is the better destination: the Rust Book at doc.rust-lang.org/stable/book/, Rust By Example, and the Rustlings kata. Those are maintained projects with exercises you run, which is a different category of artefact from a script archive.

Licence, reuse and the cost of keeping a fork

The repository is licensed CC0-1.0. Under that dedication, the scripts carry no attribution requirement and no restriction on commercial reuse. For anyone quoting a passage in a blog post or adapting a script into their own talk, that removes a layer of permissions work. It is worth noting that CC0 is a public domain dedication rather than a permissive software licence, which fits a repository of prose better than an MIT or Apache grant would.

The upgrade cost is close to zero in the usual sense, because there is no dependency graph to track and no version to bump. The cost that does exist is orientation: the README does not index the scripts, so finding a specific episode means browsing the directory. For a repository of this size that is a minor annoyance rather than a problem, but it is the reason a fork kept in sync with upstream buys you little. If you want the current material, follow the README's redirect to the Namtao repository rather than maintaining a mirror of this one.

Editorial conclusion

Clone 0atman/noboilerplate if you want to read how a Rust video script is structured, or if you are studying the presenterm and Obsidian writing workflow the README describes. Do not adopt it as a dependency, a documentation source, or a place to send pull requests for new episodes: the README states all future videos live in the Namtao main repo, and the last push to this one was on 2026-05-24. Before you build anything on it, open the scripts/ directory and confirm it holds the episode you want, because the README does not document what each file contains.

Frequently asked questions

Official sources

1. 0atman/noboilerplate on GitHub
2. Issues
3. License: CC0-1.0
4. Project website
5. README