What should I code?
Start with real demand.

Lifters who self-host their training logs in wger want to record structured data on each individual set, like whether a resistance band is single or doubled, distance from a cable anchor, or bench angle, rather than stuffing it into one free-text note per workout. Per-set reps already work, but there are no user-defined custom fields, and four separate users have asked for set-level or per-exercise annotation over the last six months. The value is logs that actually capture the variables band, cable, and calisthenics lifters need to reproduce a set.

Deaf and hard-of-hearing Linux desktop users rely on the FOSS LiveCaptions app for offline, on-device captions, but users filed fresh June 2026 requests for two missing controls: selecting one speech source instead of mixing all desktop audio, and resizing the caption window beyond a cramped single-line display. The value is making on-device captioning usable for real conversations and media on Linux without filtering games, music, and speech by hand.

Hobbyists who self-host their 3D-printing filament inventory in Spoolman want to populate spools by pulling brand, material, and color data from the community database 3dfilamentprofiles.com instead of typing each one in by hand. The requester shared a hand-rolled import script, and another user confirmed in June 2026 that it worked for them. The value is killing the manual data entry that makes inventory tracking a chore.