$ ls blog/
A running log of how each project was built — decisions, tradeoffs, mistakes, and the pieces I’d change on the next pass.
I built this to test how far a role-based learning platform could go without losing clarity, speed, or maintainability.
2 parts
Part 1 on role-based LMS design, backend/frontend split, and why I chose this stack.
Part 02
ACT E-Learning: Course Data Modeling and API ContractsPart 2 placeholder covering course entities, enrollment flow, and API response shape decisions.
Production-ready Next.js storefront with TypeScript, RTK Query data flows, responsive UI, and robust dark mode/theme support.
2 parts
Part 1 on dark mode strategy, RTK Query patterns, and resilient client-side UX.
Part 02
E-Commerce Frontend: Product Listing Performance PassPart 2 placeholder on list rendering, request strategy, and improving perceived performance.
POS-style dashboard featuring order workflows, admin management, receipt verification, and personalized recommendations backed by Supabase.
2 parts
Part 1 on modeling order states, admin actions, and receipt verification process.
Part 02
Restaurant POS: Order State Machine and Admin ActionsPart 2 placeholder on workflow transitions, guardrails for admin actions, and audit-friendly events.
Authenticated Laravel API for bug reporting with Sanctum auth, report CRUD endpoints, user stats, and program-based workflows.
2 parts
Part 1 on Sanctum auth flow, resource responses, and report lifecycle endpoints.
Part 02
ZeroDay API: Validation, Errors, and Client IntegrationPart 2 placeholder covering input validation strategy and consistent API error handling for frontend clients.