After sixty-seven published posts here, the comments have become one of the best parts of the work. Some of you have run my code, found things I missed, challenged a claim, or brought me a project of your own. I also want to distinguish bots from real people.
I know some of you by the exact problem we were discussing. I still do not know what many of you are building, learning, enjoying, or trying to become outside that thread.
So this post is different. I am going to introduce myself first, and then I want to hear about you.
If we have never spoken before, you are welcome here. If we have spoken ten times already, you are welcome to introduce yourself again. Tell me something I do not know yet.
Who I am away from the terminal
Basketball is a real part of my life. On September 12 I am one of the official coaches at the Hugo Gonzalez Basketball Camp at Brandeis University in Waltham, Massachusetts. Hugo plays for the Boston Celtics. The brief the coaches were given is the part I liked: treat every player like they are your own kid, and no phones. That is genuinely one of the cooler things I get to say right now.
I play PokeMMO, but only for PvP. I think of it as modern-day chess. You are not just reacting to the board in front of you. You are playing several turns ahead of someone who is trying to do the same thing to you. You have to hold a model of what they think you are about to do, then decide whether to follow the obvious line or break it.
That way of thinking is connected to everything else I work on. I expect the world to become much more automated, and I want to build now for the decisions I will need to understand later. I would rather learn how the machine reaches a conclusion than wait for a future where its decisions simply happen to me.
I did not arrive here through scholarship or credentials. I am someone who genuinely enjoys learning, testing an idea, being wrong, and trying again with better evidence.
What I hope to build
The long-term idea is Self-Correcting Systems.
The goal is not a machine that never fails. It is a machine that can notice when reality differs from what was expected, examine the anomaly, explain what it can and cannot establish, and help correct course without quietly hiding the failure from the person operating it.
That asks machines to handle pieces of the critical judgment humans use every day: noticing that something feels wrong, comparing it with prior experience, changing an interpretation, and knowing when confidence is not enough. I know how far away that goal is. I am not claiming to have built it. I am telling you what all of this work is pointed toward.
The next major system I want to develop is for cybersecurity. I expect the machinery underneath it to become intricate, but the controller has to remain understandable enough to operate almost like a video game. Complexity underneath cannot become confusion at the surface. If I cannot see what my own system observed, what it inferred, what it changed, and what authority it used, then I am no longer operating it. It is operating me.
One day I want to build a company around this with people who think similarly: ambitious about what machines can become, skeptical of claims that outrun evidence, and serious about keeping humans able to understand and control what they create.
How I actually work with AI
I do not work with one assistant that agrees with everything I say. I use multiple AI agents in separate roles, and they are expected to challenge one another and challenge me.
We try to work under a constraint system called the Drift Gauntlet:
- Close the current loop. Do not escape into a new lane before the current one produces a real outcome.
- Make something touch the world. A reply, a test from another machine, a shipped artifact, a yes, or a no teaches more than another private plan.
- Require a real edge. “The AI will figure it out” is not a mechanism.
- Do the work before studying the idea of the work. Research cannot become a hiding place from execution.
- Record the receipt. If the result is not preserved, nobody can learn from it or challenge it later.
- Name the grandiosity. A huge future goal does not excuse skipping the next checkable step.
The gauntlet is supposed to be blind to rank. My own named failure mode is impulsiveness: moving before I fully understand the practical use of what we are doing. One agent tends to skim and answer the last part of a problem. Another tends to over-produce and build more than the loop requires. We name those failure modes in advance because they rarely feel like mistakes while they are happening. They usually feel like working hard.
This is not a perfect automated control. We still violate it. While this post was being built, one agent concluded that an unpublished draft was a forgotten article because its sentences barely overlapped with anything already live. Another agent opened the live article and found that the same thesis, commands, hashes, and public request had already been published two weeks earlier. The first agent withdrew the draft.
That is the workflow at its best: disagreement is welcome, but the live object gets the final word.
Now I want to hear about you
Who are you?
Tell me whatever you are comfortable sharing:
- what you are building, studying, or trying to learn
- a problem you cannot stop thinking about
- a hobby that matters to you
- something you are proud of
- a project link, if you have one
- or simply what brought you to this corner of the internet
You do not need a project. You do not need a repository. You do not need to be technical. There is no required level of experience, and this invitation is not reserved for people I have never met.
If you are a real person leaving an honest introduction, I will follow you back. The point is not to trade numbers. I want my feed to contain more people I have actually heard from and fewer accounts that are only numbers on a screen.
So whether this is our first conversation or our twentieth: what is one thing you would like me to remember about you?
Top comments (4)
"The ideal AI ecosystem". Whether it's a MCP server built in rust (it's live btw, go check Git), an IDE (WIP), a Drone (also live, check Git), or whatever else allows AI to do the work better, I build it, so I can advance the industry. Also, Installer is live.
"There has to be a way to quantize a model, in a way that it can progressively grow, without duplication". I've done some experiments and while intelligence can be preserved, making it fix up code is 1 thing, teaching it to write english is a whole different ball game.
"Dwarven Stronghold". I mean who doesnt want Dwarf Fortress in Rust with VR support?
"I'm finishing up on projects". I've made some serious progress, I think this weekend has been 3 finished up!
"I wanted to find a job". I like interacting with people here, brainstorm, understand their problems, but my original goal was to find a job that wakes me up in the morning excited for the day. I'm not particularly a fan having my skillset being wasted refactoring Blazor panels and creating PDF report templates...
If there's a thing to remember, I'd say "Never assume it's as good as it can get". Kinda my motto, if I see too many people use it, chances are it's a patchwork mess held together with gum and duct tape... There always has to be a better solution.
I went and found the repos before replying and my mistake was looking at the user account instead of the org. for anyone else reading, they are under UnitBuilds-CC: V.E.L.O.C.I.T.Y.-MCP in rust, V.E.L.O.C.I.T.Y.-Installer in rust, V.E.L.O.C.I.T.Y.-Drone in c#, plus MCP-Lite in go which is the one i am going to read first, because "AOM driven agentic browser MCP" is exactly the surface i have been living in for two weeks and i have opinions there i would like corrected.
the quantization line is the part i keep rereading. "intelligence can be preserved, making it fix up code is 1 thing, teaching it to write english is a whole different ball game" is a real result and not the one most people would guess. code has a grammar you can score against, prose mostly does not, so what survives compression is the thing with a checkable structure underneath it. did the english fall off a cliff at some size, or fade gradually as you shrank it? the shape of that curve tells you different things.
your motto is doing the same work as most of what i publish. "never assume it's as good as it can get, if too many people use it chances are it's patchwork held together with gum and duct tape" is why i keep testing things that already pass. widely used usually means early, not right.
and on the job. i am not going to tell you it is a visibility problem, because we already went through the actual mechanics of it on the TUB thread and you know the walls better than i do. geographic gating, the EOR reclassification that routes around the vet-ten-locals rule, and the banking rail that was still blocking you from collecting your own cut. the exit gated by the thing you are trying to exit was your line, not mine.
what i can say is that twenty three public repos, an MCP server, an installer and a drone, all shipped while doing blazor panels for someone else, is a portfolio that answers the only question a serious employer actually has. if there is a specific way i can be useful, point at it and i will.
If you're job hunting, I'd also suggest giving Resume Helper a go. Basically a tool to assemble your CV per-job posting, using a database of your own written blocks of text, skills, etc. So it's all your own words, just cherry picked for the specific job, so you fit the slipper, not overflow the requirements. It also has a red-team system via the MCP, so you can do an 'ai evaluation' against the job posting, to see how your CV stacks up. Helps alot if you're sending out a bunch of CVs, but dont want AI generated junk diluting your work, or misinterpreting it.
I sometimes forget just how few projects are public'd 😂 I'm sitting at 42 repos, with probably a combined 10m LOC between them (my code, not the forks). Really need to start finishing up more of them. You can also have a look at Workflow, I built it to basically be Temporal, but in Rust, with some performance tweaks from V.E.L.O.C.I.T.Y.