hours of Excel a month, eliminated
Asia Builders ERP now runs projects, payments, and reports end-to-end
Software engineer · Islamabad
Three years building web platforms and ERPs for startups, agencies, and construction companies, the kind of software a business ends up actually running on, not the kind that gets replaced in six months.
hours of Excel a month, eliminated
Asia Builders ERP now runs projects, payments, and reports end-to-end
cost reduction
Swoop Inc mobile dev: 3 apps shipped in 4 months, 40% faster delivery
team efficiency gain
Better tooling and processes · Hill Country Coders
Lead · 2024–present
The accountant was spending 40 hours a month in Excel. Now they have a full ERP: projects, transactions, vendors, documents, reports, and a role-based dashboard. Built for Asia Group of Companies.
13 production tables · 50+ REST endpoints · 10 feature modules · 6 DB migrations
6 report types × PDF + Excel: P&L, Expense Breakdown, Vendor Payment, Govt Audit
Safe file handling so a failed save never leaves an orphaned document behind
Independent per-section dashboard queries, so one failure doesn’t blank the screen
3 roles (OWNER · ACCOUNTANT · REVIEWER) with proper access control
Lead Engineer · Hill Country Coders
Multi-tenant task management platform that replaced Excel-based tracking and drove a 10–12% company-wide efficiency gain in under six months.
Internal and external project tracking · skill matching · priority levels
Email notifications · separate data per client · real-time companion chat
Low-cost full-featured internal messaging for Hill Country Coders: file sharing, rich text editor, real-time delivery. Companion to WhatsNextPlease.
Lossless file compression implementing Huffman coding from scratch: streaming I/O, a custom generic priority queue, comprehensive tests. Built to learn Go’s data structures hands-on.
Private PWA for tracking shared commitments: a promise journal with reminders, attachments, push notifications, and a Supabase Realtime backend. In progress.
Merged fixes in zen-browser/desktop (★ 42k: sidebar drag-flicker root-caused to a dragleave feedback loop) and Melkeydev/go-blueprint (★ 8.9k: bridged the PORT env var across the Go/Vite boundary).
Most software problems are operations problems.
The Asia Builders ERP started as “the accountant spends 40 hours a month in Excel.” WhatsNextPlease started as “the team doesn’t know who owns what.” I design around the real problem first, and let the technical decisions follow from that, not the other way around.
I read the actual error before searching for it online, and I trace bugs back to their real cause instead of patching the symptom: that’s what stops the same issue from resurfacing at 11 pm on a deadline day.
I design for things going wrong: a failed save shouldn’t leave orphaned files behind, one broken part of a dashboard shouldn’t blank the whole screen, and deleted records stay recoverable instead of disappearing without a trace.
Working software over perfect software, but the working version ships with tests.
The languages, frameworks, and tools I actually reach for day to day — not a list of everything I’ve ever touched.
Core languages I write day to day, across backend and tooling.
APIs, services, and the databases behind them, running in production.
Interfaces built with React and Next.js, styled with Tailwind.
Deployment, storage, and infrastructure for real traffic.
Automated tests that catch regressions before users do.
Design, editors, and CI that keep the day-to-day moving.
Computer Engineering graduate from NUST, Islamabad (2023). Started writing production code in 2021: blockchain social platforms, then mobile development at Ensemble UI, now leading engineering at Hill Country Coders.
Two competition results worth mentioning: Top 10 Startups at iCreate-21 (PIEAS) and Runner-Up at FICS-2022 (NUST), both with Gul-e-Shaor, which went on to NIC incubation in Peshawar.
I break down real database and backend problems on YouTube — no slides, just the actual query plans and benchmarks. From the System Design playlist:
How databases handle tables with billions of rows without falling over, and where partitioning can actually hurt you.
Watch on YouTubeA real 50-million-row case study of an index Postgres refuses to use, and why the query planner is right to skip it.
Watch on YouTubeThe two core indexing structures every backend engineer should know, and how each one finds a row in milliseconds.
Watch on YouTube