Skip to content

I will audit, review, and fix your vibecoded shitshow.

Deploy The Autist

Highly weaponized, military-grade autism solving your engineering challenges.

Shipping software
19 years
Systems focus
AI / ML
Execution range
Rust + React

How the autist makes it sane

You hire me for the ugly systems work: sit with the broken thing, spot contradictions, delete noise, and make the code safe enough for users.

  1. 01

    Give me the ugly path

    Repo, branch, bug, outcome. I start at the contradiction.

  2. 02

    I lock onto the pattern

    I trace the pattern across state, data, prompts, and deploys.

  3. 03

    We ship the boring fix

    Commits, tests, notes, and code the team can explain.

What you brought me

The app works until reality touches it: auth, users, payments, weird state, and the second click.

AI got you a demo. My autistic focus earns its keep after the dopamine, where I stay with contradictions until I can name why the code fails.

What you hire me for

Pick the engagement that matches the failure path. Audit, repair, training, and technical leadership all end in written decisions and working code.

You pay for obsessive attention to the part the team keeps talking around, then the discipline to make it boring.

Shit I shipped

Production damage, shipped systems, and code that had to keep running under real constraints.

Rust services, React migrations, realtime pipelines, AI runtimes, latency work, and the details my brain refuses to ignore.

Where autistic focus pays off

You have a repo full of plausible answers and no proof the product can survive users. I bring autistic pattern recognition, senior engineering judgment, and the patience to chase the weird path until the fix is clear.

Software Engineering

  • Critical path shipped
  • Production seams fixed

Frontend Engineering

  • State traced
  • Forms hardened

Consulting

  • Damage map
  • Scope cuts

VibeCode Unfucking

  • Repo triage
  • Failure path fixes

Effective AI Use Workshops

  • Prompt boundaries
  • Review habits

AI Systems and Agent Tooling

  • Tool contracts
  • Eval loops

Contact me

Another prompt adds code. I find the contradiction.

Contact me

What you get

No vague retainer fog. You get the autistic inspection first: what breaks, what matters, and which repair buys the most safety.

  • Autistic pattern review across folder structure, state, data, failure paths, and contradictory code.
  • A blunt damage report written for humans: keep, cut, rebuild, fix first.
  • Senior implementation across React, TypeScript, APIs, AI workflows, data, and deployment seams.
  • Handoff notes with exact decisions, remaining risks, and next cuts.

Proof the autist can ship

I have shipped software for 19 years and spent the last 2 fixing vibecoded SaaS messes for founders. The useful part is the same: pattern recognition, low tolerance for sloppy abstractions, and enough focus to finish the repair.

Shipping software
19 years
Fintech, cloud, commerce, AI-heavy products, and code with real consequences.
AI systems
AI / ML
Model routing, RAG, MCP, vector databases, and agent workflows that need contracts.
Build range
Rust + React
Rust backends, React interfaces, latency work, and data flow the team keeps hand-waving.
Ownership
Lead roles
Founder, staff-level engineer, and IC who can make the call and write the code.

blprnt

Founder / Lead Engineer

Built a local AI execution runtime for autonomous teams: Rust coordinator, durable state, multi-provider model routing, and a React/TypeScript operating surface.

  • Rust
  • TypeScript
  • React
  • SurrealDB
  • Docker

Amazon Web Services

Software Engineer Level 6

Led frontend modernization inside AWS, moving a legacy Java UI toward React and TypeScript with tighter delivery, accessibility, and review standards.

  • React
  • TypeScript
  • Webpack
  • Java

Trading Systems & Consulting

Consultant / Systems Engineer

Delivered low-latency Rust services, real-time ingestion pipelines, and data-dense React workflows across fintech, ecommerce, and SaaS products with hard failure boundaries.

  • Rust
  • React
  • TypeScript
  • Node.js
  • PostgreSQL

Why hire an autist instead of asking the bot again?

The bot drafts from context. I check the parts it treats as disposable: four owners for one value, auth that lies in one route, and tests that missed the bug.

Decision pointHire An AutistAI-only passTypical agency
First useful outputA blunt map of what is broken and where to cutMore code on top of the same confusionDiscovery before someone opens the repo
Debugging styleAutistic pattern lock across state, data, prompts, and deploysLocal guesses from whatever context fitsTickets routed through layers
Best fitUgly systems, AI slop, brittle UI, strange backend behaviorFresh demos and shallow fixesGreenfield builds with room for meetings
CommunicationSpecific written tradeoffs with no softened risk languageConfident paragraphsDecks, standups, and consensus fog

Before you ask

The questions founders ask after they send the repo and before they decide whether the blunt branding is a bit.

How fast can you start?

Within a week in most cases. Send a clean brief and I can move sooner. A vague calendar for next quarter belongs with someone else.

What if my code is too far gone?

Then I say so. The damage report gives you the least stupid next move: fix, rebuild, cut scope, or bury it.

Do you do retainers or fractional work?

Yes. Short audits, fractional advisory, and fix-and-ship blocks work. The scope follows the failure path.

Can you teach my team to use AI without setting the codebase on fire?

Yes. I teach teams where AI helps, where it lies, and how to review generated code before it mutates the product.

What does it cost?

The mess decides. Audits stay contained. Last-mile fixes scale with risk, ownership, and how much generated code we need to unwind. I quote numbers, not vibes.

Are you autistic?

Diagnosed. My autism shows up in the work: pattern lock, low tolerance for fuzzy logic, and long focus runs on problems other people avoid.

You should see the repair path before you pay for it.

Dark engineering desk with monitors, hardware boards, and amber task lights
Find the contradiction the bot pasted over.
Abstract code forensics panels suspended above a dark workbench
Turn pattern recognition into a repair path.
Amber-lit server corridor and deployment bench in a dark data center
Force the demo to meet production.
Dark handoff table with abstract architecture diagrams and repair notes
Leave the next engineer a map.

Contact me

Send the repo, the broken flow, or the AI-generated knot the team keeps avoiding. I will read it, name the failure path, and tell you where my attention helps most.