Enterprise-style ASP.NET Core MVC web application for aircraft fuel transaction management with role-based access, reporting, dashboard analytics, PDF invoice generation, Excel export, and CI/CD deployment workflow.
One problem. Two design directions. Which would you choose?
For AEGIS / 001.05 . Traffic Operations, we explored two approaches to the same challenge: helping city operators understand congestion, incidents and network-wide disruptions without overwhelming them with information.
Both solve the same operational problem. Different approaches to hierarchy and interaction.
If you were behind the control desk . Option A or Option B?
I just relaunched my site, alireza.work, a one-page look at what I build and how I work.
I'm a senior full-stack & AI engineer in Cyprus. Over the last 7 years I've built:
→ a multi-tenant commerce platform running ~300 stores, with an AI operator on 100+ MCP tools
→ the backend of a crypto exchange with 100K+ users (as team lead)
→ open-source agent tooling for NestJS
What I help with now:
• AI products, built end to end, from architecture to real users
• Apps built with Lovable, Bolt, Base44 or Cursor, made secure and production-ready
• AI agents that plug into your existing business systems
If you have a prototype that works in the demo but you're nervous about real users, send me the repo. The first call is free.