Independent software & experiments

Useful ideas that
got a little out of hand.

Software, tools, games, infrastructure, automation, and the occasional weird idea that started with “why doesn’t this already exist?” and somehow ended with its own database.

last-weeks-project.cs

        
What gets built here

A fairly unreasonable range of things.

The stack changes with the problem. The common thread is practical software that removes friction, gives people more control, or explores an idea far enough to find out whether it should exist.

01

Developer & Infrastructure

Automation, networking, APIs, certificate tooling, self-hosted services, deployment helpers, and utilities built to make technical work less annoying.

02

Applications & Utilities

Desktop and web applications focused on real jobs, clean interfaces, local control, and doing one thing well without turning it into a subscription ecosystem.

03

Learning & Study

Practice exams, flashcards, simulations, assessment tools, and study software designed around actually learning the material instead of just clicking through it.

04

Media & Creative Tools

Readers, conversion tools, audio workflows, local AI experiments, media management, and software for turning content into something more useful.

05

Games & Experiments

Game systems, Unity projects, multiplayer utilities, procedural ideas, and prototypes that are allowed to be weird as long as they are interesting.

06

Distributed & Cryptographic

Peer-to-peer architecture, encrypted identity, verifiable randomness, distributed storage, permissions, and other ways of asking whether a server really needs to be in charge.

A few examples

Projects that escaped the idea folder.

Some are polished products, some are open source, some are experiments, and some are still evolving. That distinction tends to become fuzzy around version 0.3.

The general philosophy

Build the thing.

If the tool I want doesn’t exist, that sounds like next week’s project.

01
Make it useful.Solve a real annoyance, remove friction, or answer an interesting technical question.
02
Keep it understandable.Complexity is sometimes necessary. Making it everyone else’s problem is not.
03
Automate the boring parts.Computers are remarkably good at repetition. Let them suffer instead.
04
Give users control.Local-first and self-hosted are great when they make sense. Data should not become ransom just because software touched it.
05
Ship, learn, improve.An imperfect working project teaches more than the immaculate one still living in a folder called “final-final-v3”.