Three apps, three stacks, one AI-assisted workflow — a practical writeup
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...