01 / Origin · Ontario, Canada
Aleks Manov
Software engineer · Transportation supervisor
I write software for the kind of operations I have spent a decade running.
Nine years building full-stack and mobile systems, alongside twelve years in transportation — dispatch, fleet, emergency response, and supervision. The second half is not a detour from the first. It is the reason I build the way I do.
- Software
- since 2017
- Operations
- since 2014
- Public repos
- 7 curated
- Based
- Ontario, CA
What operations taught the engineering
Twelve years of dispatch, driving, and supervision is not a line on a résumé that happens to sit under the technical one. It is where these five constraints came from, and they decide most of what I build.
A slow screen in dispatch is a truck idling and somebody standing on a shoulder.
I treat response time as a property of the job being done, not a number on a dashboard. That decides where caching goes, what renders on the server, and which work is allowed to happen while someone waits.
Nobody reads carefully during an incident. They read the top line and act.
Interfaces I build state what is happening, what failed, and what to do next, in that order. Ambiguous state is a defect, not a styling problem.
Coverage drops in underpasses, industrial parks, and most of rural Ontario.
Offline behaviour and retry semantics are design decisions made up front. A mobile client that assumes connectivity is a prototype, whatever it says on the store listing.
Hours of service, inspections, and incident records get audited by people who were not there.
Compliance is a data-modelling problem. Getting the schema and the audit trail right at the start is cheaper than reconstructing history from logs a year later.
The dispatcher answers for the call, not the software that suggested it.
That is a reason to make failure loud, defaults conservative, and destructive actions hard to take by accident. Silent degradation moves the blame onto the person holding the radio.
Public work
Everything below is public and hand-picked — seven repositories out of the account, chosen for what they show rather than for what they scored. Select one to see what it uses; select a technology or a domain to see what used it.
No filter applied.
Repository facts come from a snapshot committed to this site’s repository, last refreshed . The site makes no request to GitHub, so a GitHub outage cannot break this page — and no private repository is ever read, named, or counted.
Track record
One list, both tracks, newest first. They overlap rather than alternate — the freelance development ran straight through the towing years.
Apr 2025 — present
Operationscurrent
Transportation Supervisor — Shred-it
Ontario, Canada
Frontline transportation operations in a high-volume, unionized environment: fleet performance, labour management, safety compliance, cost control, and customer service delivery.
Aug 2017 — present
Softwarecurrent
Software Developer — Independent
Ontario, Canada
Full-stack client work. Recent engagements include edge request filtering and origin selection on Cloudflare Workers, a Next.js storefront over Strapi with Stripe Checkout, and an Express and PostgreSQL API behind a content management system with a Redis cache in front of it.
Jan 2023 — Jan 2025
Operations
Operations Manager — SOS Towing
St. Catharines, Ontario
Business operations and fleet management: team leadership, emergency response coordination, client relationships, and working relationships with provincial road-safety and transport regulators.
Mar 2022 — Jan 2023
Operations
Dispatcher — A Action Towing and Recovery
Burlington, Ontario
Dispatch for a multi-truck operation — route and response-time decisions, coordination between drivers, clients, and emergency responders, and the record-keeping that has to hold up afterwards.
Nov 2016 — Jul 2017
Software
Android Developer — A Action Towing and Recovery
Burlington, Ontario
Built the company's dispatch application: Java and the Android SDK, Google Cloud API integration, and real-time location tracking for the trucks in the field.
The join. I wrote a dispatch tool for an operation whose trucks I had driven and whose calls I would later take.
Jun 2014 — Mar 2022
Operations
Tow Truck Driver, then Owner-Operator — Independent / A Action Towing and Recovery
Ontario, Canada
Towing and recovery: emergency response, accident scene management, safety and regulatory compliance, and — after moving from company driver to owner-operator — the business side of running a truck.
Working stack
Grouped by what each thing does in a running system. Each entry says where the claim comes from — a public repository, the GitHub profile, a dated role, or a freelance engagement. Nothing is listed because it looked good in a list.
Interface
What people actually touch.
Mobile
Devices that leave the building.
Backend
Where the decisions get made.
Data
The part you cannot rebuild from a backup of the frontend.
Infrastructure
Where it runs, and what happens when it stops.
Tooling
The workshop, not the product.
Education
2022 — 2024
Computer Science Diploma
Software Engineering · Sheridan College
Get in touch
If any of this is relevant to something you are building, the fastest route is email.