Build is like Makefile for single files

Generic drop in Makefile. GitHub Gist: instantly share code, notes, and snippets.

Ultimate collection of free tools for MVP or online project

Hey HN! We just launched open sign up on Buildstash. It's a platform for managing and sharing software binaries. I'd worked across game dev, mobile apps, and agencies - and found every team had no real system for managing their built binaries. Often just dumped in a shared folder (if someone remembered!). No system for versioning, keeping track of who'd signed off what when, or what exact build had gone to a client, etc. Existing tools out there for managing build artifacts are really focused on package repository management. But miss all the other types of software not being deployed that…

I love C and C++, but setting up projects can sometimes be a pain. Every time I wanted to start something new I'd spend the first hour writing CMakeLists.txt, figuring out find_package, copying boilerplate from my last project, and googling why my library isn't linking. By the time the project was actually set up I'd lost all momentum. So, I built Craft - a lightweight build and workflow tool for C and C++. Instead of writing CMake, your project configuration goes in a simple craft.toml: [project] name = "my_app" version = "0.1.0" language = "c" c_standard = 99 [build] type = "executable"…

A developer's machine accumulates tools fast. A Rust CLI you compiled last year, a Python formatter installed via `uv`, a language server pulled from npm, a terminal emulator from a curl script, a Go binary built from source. Each came from a different package manager, each with its own install incantation you half-remember. I wanted a way to declare what I need without adopting a complex system like Nix or Ansible just for a single laptop. The result was a plain old Makefile. I wrote a short post on using Make (along with a tiny bash script and fzf) to create a searchable, single-command…

Build anything via containers