Software for One

Opus 4.5 with a plan mode is enough for me: it asks clarifying questions to map out the design space, it covers fiddly parts, it generates good unit/integration tests.

I have seen it cheat by deleting existing tests, since it's single-mindedly focused on the problem I give it. I've not used an LLM-to-review-an-LLM, but when I've used an LLM to review my own work, it notices when there are unrelated changes in my commit/working copy.

Besides, all of your critique is how I've heard product managers speak of human developers! And a tool needn't be perfect for it to be useful.

There's one in particular that I use quite often and have for about a year, vibed for myself: it's a chat interface that walks you through processing an emotional or difficult moment, following a process / workflow. Supports Martin Seligman's ABCDE and Byron Katie's "The Work". Two techniques that I found most useful to improve my thinking and responses to difficult situations. You converse with it, and it leads you through the stages of the selected flow. More than a system prompt - it tracks and progresses through the workflow at the right times, and you download a consistent pdf of key details from the "session" at the end for your records.

The thing is, I can't sell it. I don't even think I can open source it. It's mental health (minefield of legal and ethical issues), and would probably breach copyright, trademark etc law.

Yet it's very useful to me. I guess it's the equivalent of making a system to do these things at home, like prompt cards or key points taken from the books, with a well formatted note taking structure. Except it's way easier because you just chat like you're talking to someone.

I would never have spent time building this. But now it's so cheap and easy to do.

There's existing stuff for this but making a personal extension to this should be very well possible too.

I have written so much software for one... I cannot recall everything. I use some of it daily:

- I have my custom elf(glibc)/linux distro

- I use my own ffmpeg based x11 media player (will have an update for wayland).

- Since the "geniuses" at gogol blocked all accounts not using whatwg cartel web engines and blocked all self-hosted SMTP servers (I do not pay the DNS mob, then IP literals, which is stronger than SPF) to exchange with gmail.com users (now prisoners), I have my very own simple noscript/basic HTML servers (messaging, file transfer, openstreetmap browsing, etc). Unfortunately, most are C written from linux instead of assembly (at least, I removed most of the time the libc dependency with direct syscall programming). IPv6 is making everything internet software muuuuuuch easier to implement: I am lurking at an IPv6 only, super idiotic and real time voice/video/text/file transfer protocol, probably based on SIP (the main issue are randomly generated IPv6 addresses from mobile internet, which may require a mini-server for IPv6 address exchange, BAAAAAAAD!).

- Ofc, I still have my own minimal SMTP server (and a SMTP client to send emails), because there are still honnest people on internet. mutt forever.

- I am trying to build a RCS for linux, aka a Reduced Command Set with near direct hardwiring to linux syscalls. I lose comfort, but knowing that I removed giga tons of bloat feels so much satisfying it is worth it by light years. I will have to code my own command shell one day.

I still have C code since I currently need portability on IP-LOCKED ISAs (arm and x86-64). But I wish for RISC-V to be a success, namely as a modern, very often hitting the 'sweet spot' in technical design compromises, NON-IP-LOCKED ISA. I am writting much software in RISC-V assembly now... which I run on x86-64 with a small interpreter (written in x86-64 assembly)... trying to fix the bloat and kludge from corpo-like open source software (including the SDK).

Right now, I am writting my own wayland compositor using that framework. I was not expecting window management to be a bazillion of little things to do everywhere. And even if a wayland compositor is several orders of magnitude smaller and leaner than a x11 server, it ain't that a small project (ofc, I implemented myself the wayland wire protocol, no external libs here).

In my 'trying to fix the bloat and kludge' from corpo-like open source, I force myself to use my own exe/dynamic lib format for modern hardware (so lean, a simple RFC will be enough, and no more loader bloat/kludge). But I am scared at the abominations which are all the requirements of classic computer languages to run: I would like a mesa vulkan driver, but there is still c++ (super BAD) in there which makes porting to an alternative dynamic lib format a living hell, non trivial C won't be that easy neither (for instance the abomination of the ISO __thread keyword, amazing bright minds there). Taking perspective from that, I wonder why anybody sane would add on top of that a big runtime requirement??

And what people doing that have to keep in mind: IRL can put a violent stop to all of this.