đ Ah yes, the age-old dilemma of documenting your messy dev setup using a
#Makefile, because who *doesn't* love Makefiles? đ€ By all means, declare your devotion to tech nostalgia as you attempt to tame your chaotic toolkit with a file format that turns every installation into an archaeological dig. đŠ
https://thottingal.in/blog/2026/03/29/home-maker/ #TechNostalgia #DevSetup #ChaosToolkit #Documentation #HackerNews #ngatedHome Maker: Declare Your Dev Tools in a Makefile
Your laptop has ripgrep, installed via cargo install. ruff is there too, via uv tool install. golangci-lint came from go install. bash-language-server was npm i -g. Neovim was a tarball download. Kitty was a curl script.
Six months later you get a new machine, or you just want to upgrade or reinstall. What do you even have installed? How did you install each one? Which version? Good luck.
This is a small system that answers those questions â a single Makefile that declares every tool you care about, grouped by purpose, with one command to install anything.
Today, I'm so happy to have released a new version of the open tracing #chaostoolkit extension that properly supports #opentelemetry
https://chaostoolkit.org/drivers/opentracing/
Your #chaosengineering experiments deserve to be visible.
Open Tracing/OpenTelemetry -
Chaos Toolkit
I have so many
#chaostoolkit extensions, each on their own repository. I do wonder if I shouldn't collate them into a single repository.
#monorepoLovely that
#chaostoolkit was the first
#OSS contribution for one of our community member :)