Posts

Showing posts from August, 2026

Three apps, three stacks, one AI-assisted workflow — a practical writeup

Image
Sharing the technical details of three systems I built with an iterative AI-assisted process. Different domains, different stacks, same method. The useful part is where the process held and where I had to take over. TRM — Training Management System Stack: ASP.NET Core 8 MVC, PostgreSQL, Dapper, ASP.NET Core Identity with custom Dapper stores, QuestPDF, SMTP. Three roles with real separation: Admin manages users, roles and course requirements; Teacher creates courses, uploads materials, marks attendance; Student enrolls, accesses materials, downloads certificates. Worth noting: Custom Identity stores over Dapper. Identity assumes EF Core. Wiring it to Dapper stores was manual work — the generated starting point needed real correction. Certificates generate as PDFs at completion (QuestPDF), driven by attendance-based completion percentage. Audit fields on every table ( created_by , created_date , modified_by , modified_date ) — decided up front, which meant it never had to be retrofi...

Building an MES with AI-assisted development — what actually worked

Image
I want to share a practical breakdown of building Basirah MES , a Manufacturing Execution System, using an iterative AI-assisted workflow inside VS Code. Posting this because MES is a genuinely hard domain and I think the friction points are more useful than the highlight reel. Modules built: Production management (production orders, work orders, scheduling) Quality control (inspections, certifications, compliance tracking) Inventory (real-time tracking + material transactions) Equipment monitoring (status, maintenance schedules, OEE) Shop floor control (barcode scanning, real-time tracking, operator UI) Analytics and reporting (KPIs, performance metrics) Stack: Backend Node.js / Express, PostgreSQL, JWT, WebSocket, Docker Frontend React + TypeScript, Material-UI, WebSocket client Data Knex migrations + seeds Docs Swagger at /api-docs Tests Jest (backend + frontend), Cypress for E2E Workflow: Requirements first — modules, features, stack, database. Written down, ...