About · Alex Shortov · End-to-End Software Engineer & Solutions Architect

Every role on the org chart.
One engineer.

In 2001 this job was called programmer. Since then it has been called full-stack developer, solutions architect, engineering manager, CTO. I have held every one of them, usually at the same time - and with Claude Code they collapse back into a single person who takes a business problem from the first call through design, code and testing to running software.

Alex Shortov

I wrote my first production code in 2001, on a suite of marketing software. For the next six years I ran web development, digital marketing and the whole e-commerce operation for a distributor - which is where I learned that code only counts when it moves a business number.

In 2008 I founded Data Subsystems and have run it since: 130+ projects for clients in payments, e-commerce, manufacturing, real estate, crypto and media. At some point I noticed my real product isn't code. It's the moment an owner stops worrying about the system - because it runs without me: documented, handed off, on autopilot.

For fifteen of those years the engine behind the speed was ninja teams - small squads of exceptional developers I hired, led and kept for years, running up to ten client engagements in parallel. Clear scope, tight feedback loops, ruthless review, working software every week. Management was never the product; it was how I kept ten clients shipping at once. Those people did not go anywhere: twenty-five years in the industry left me a network of the best I have worked with, and when a job is bigger than one person, a vetted team is up in days.

Today I run the exact same playbook with a different team: AI agents, orchestrated the way I used to run people. Same discipline, same gates, same honesty about scope - but the cycle time dropped from weeks to days, the team never sleeps, and I am back to writing most of the code myself. Nearly ten thousand commits in the last ninety days, and my review is still the gate before anything goes live.

My client relationships are measured in years; the longest ran seventeen. When one client's fashion-retail chapter ended, we didn't part ways - I helped him turn the same operation into a fine-mineral business. I like long games and second lives: my own 2007-era domain died in a Google update and came back sixteen years later as a startup radar.

These days I also write about startups: The Shortov Report - a weekly on where founders and venture money are heading, by email today and on YouTube next. After twenty-five years of building software for them, I have opinions worth publishing - and a radar to check them against.

How one engineer ships like a team

Then

Hand-picked squads of senior developers. Hiring took months, great people were scarce, and scaling meant payroll.

Now

A workshop of AI agents running the same discipline: scoped tasks, code review, tests, deploy gates. Scaling is a config change.

What never changed

Honest scope before code, weekly ships, and one engineer who reads every line that goes to production.

Principles I work by

Honest scope first.

I'll tell you what not to build - before any code, at my own expense.

Numbers over vibes.

I built a 20,000-company radar because opinions about startups are cheap and data isn't.

Done means autonomous.

A project is finished when it runs without me.

Nothing wasted.

Old domains, old codebases, old businesses - most "legacy" is an asset waiting for its second life.

Craft in the last 2%.

The details a client feels but can't name.

Now · September 2026
  • Building a real-time market-data recorder for live-auction marketplaces - private APIs, sessions, rate limits, evidence
  • Scaling the AEO Content platform - audits to AI article writing
  • Client builds: a parts-search engine over industrial catalogs and an operator console for industrial machinery
  • Writing The Shortov Report every week from 20,000+ tracked companies

Off the clock

3D printing is my hobby, and it's a family one - my son and I build things together. The current project: a motorized RC SailGP yacht, designed parametrically and printed at home. Same engineering instinct, smaller blast radius.