I own the judgment.
Scope, architecture, product choices, code review, QA, and the final call on what ships stay with me.
Independent product studio
Senior-led software development, with AI used carefully.
I'm Alex. I shape the product, direct an expert coding AI, review the code, test the result, and stay accountable through release.
EyeNineOpen-source endpoint monitoring, built and tested in public.
How the work is divided
No mystery team.
You work directly with the person making the product and engineering decisions.
The AI expands the bench.
I use expert coding agents for implementation, analysis, and fast iteration inside a defined, reviewed process.
You see the evidence.
Working slices, acceptance criteria, test results, and known tradeoffs keep progress inspectable.
First public proof
EyeNine keeps endpoint monitoring local and readable.
It is a real desktop application—not a concept screen. The source, setup, tests, release limits, and issue history are public.
- HTTP, TCP, ping, and DNS checks
- Accessible light and dark interfaces
- SQLite history, exports, alerts, and SLA reporting
- Repeatable visual QA at difficult sizes and states
Matrix view · Real application data from the running desktop build
Services
Three ways I can help.
The engagement follows the uncertainty. Clear scope gets a clear price; open-ended work stays flexible.
Application development
New products, focused MVPs, substantial features, and internal tools. The scope starts with the user and the outcome—not a preferred stack.
Web design and development
Fast, accessible business and product sites with clear writing, responsive layouts, and no page-builder residue.
Product and engineering help
Architecture, diagnosis, code review, rescue work, and ongoing implementation when the problem is still taking shape.
Process
A short loop, repeated carefully.
Frame the real problem
You and I agree on the user, the constraint, the useful outcome, and what done means.
Build in visible slices
I direct the implementation, review the code, and keep each change small enough to judge.
Try to break it
Realistic data, awkward sizes, keyboard use, failure states, and repeatable checks come before release.
Hand over something legible
You get the code, the decisions, the known limits, and a release path another developer can follow.
AI makes the loop faster. It does not remove review, testing, or accountability.
A good first message
What are you trying to make better?
Send the outcome, the current obstacle, and any real constraints. A polished brief is optional.