Building TerminalNexus, a Windows command management center that puts Git, SSH, and command history in one window. Shipping publicly, sharing what I learn.
FSD takes the same left turn three different ways on three different days. Same intersection, same weather, same time. It doesn't drive like a car following rules. It drives like a chatbot re-rolling the dice every time you ask.
The bike was half the cost of cycling. The other half is a slow checkout cart that never closes: a stem, wider tires, a floor pump, a headlight that actually lights the road instead of politely announcing I exist.
The five commands I run to spin up any project are buttons in my terminal, not muscle memory I have to relearn every time I switch machines. Boring, reliable, mine. That's the whole pitch.
Adulthood is mostly just maintaining things nobody warned you about. The car, the bike, the body, the house. You don't really own hobbies so much as adopt dependents that all need new parts on the same weekend.
I stopped switching to a separate Git app. Right-click the file, the diff renders right there in the terminal, stage it or don't. One less window to alt-tab to, and my brain is noticeably quieter for it.
I have a TerminalNexus button that runs daily at 7am, dumps the output to Slack, never opens a visible terminal.
Background PowerShell. The schedule lives in the command, not Task Scheduler. One less Windows panel to remember the name of.
Same prompt Monday and Friday, two different answers, and we call that intelligence. Determinism used to be the entire point of a computer. We traded it for vibes and now half of debugging is asking the model why it changed its mind.
The part of FSD the hype crowd won't say out loud: the bugs rotate. A phantom brake gets fixed, disappears for a few updates, then strolls back in like an old roommate. I've watched the same issues cycle for two years.
Nobody warns you that going tubeless means periodically holding your wheel up to your ear to confirm the sealant still sloshes. I am out here shaking a tire like it's a wrapped gift, listening for life.
If you didn't write it line by line, you didn't review it line by line.
A pre-commit OWASP scan reads the diff so you don't have to. Catches hardcoded creds, SQL injection patterns, the boring stuff autocomplete loves to inline.
Two seconds added to every commit.
vs the half day spent rotating a leaked key, mailing the security team, and pretending you knew the whole time.
A pre-commit security scan is the cheapest insurance any dev tool ships with.
Cursor and Copilot will paste an API-key-looking string into your code if it fits the next-token pattern.
You will not notice. The pre-commit scan in TerminalNexus will. OWASP Top 10 on whatever just changed, before the push goes out.
Default terminal scrollback is 1,000 lines.
Bump it to 100,000 and stop losing build output the moment you scroll up. Most emulators hide this setting three menus deep, which tells you how rarely the designers needed it.
1,000 auto-backups, kept every app start. Settings as encrypted ZIP, timestamped.
The day you actually need one is the day you stop calling backup retention 'paranoid.' Everyone has that day eventually, and the people who don't are the ones who lost the file.
{{{ssh_prod}}} dropped into any command button.
Resolves at execution to the full ssh -i keyfile -o ServerAliveInterval=60 user@host with your tunnels. 'Open prod and tail the logs' becomes one click instead of a paste-this Notion doc.
My TerminalNexus commit flow runs an OWASP Top 10 scan on changed files before the commit lands.
Two seconds added. Worth it the day it catches a hardcoded key before the push goes public.
Auto-prefix every commit with the branch name.
BUGFIX-9999: your message.
The 'every commit must reference a ticket' policy stops being friction the moment the editor does it for you instead of the human.
Vibe coding means you didn't read every line.
The pre-commit scan reads them for you. OWASP Top 10 and CWE Top 25 on changed files, before the commit lands. Two seconds, runs in the background, blocks if it finds something with teeth.
If you have 500 followers and post into the void, your odds of finding the right reader are bad.
If you don't post at all, the odds are zero.
Build out loud anyway. Break-even is one good message reaching one right person.
Right-click any file in the terminal pane. Stage it, diff it, run a security scan on the changes, open it in your editor.
Context menus on terminal output sound trivial until you stop alt-tabbing thirty times a day.