Technical notes, project documentation, and lessons learned across software, DIY, writing, and more.
Gmail strips your style tags and overrides your link colors. Here's how we build branded HTML emails that survive every client using inline styles and C# 11...
GDPR says users can request erasure. Most apps flip IsDeleted. We soft delete for referential integrity, then anonymize every piece of PII. The account is gone.
Same codebase, same deployment. API routes use JWT bearer tokens, web routes use cookies. A 10-line policy selector makes them coexist without conflicts.
Ten background services running on a $5/month shared hosting plan. No Hangfire, no Quartz.NET — just BackgroundService, Task.Delay, and smart scheduling.
Our entire game runs on a $5/month SmarterASP.NET plan. No Docker, no CI/CD, just MSDeploy and every workaround for shared hosting constraints.
Three fixes. Three confident explanations. Zero progress. After a failed client demo and two weeks of pain...
Step-by-step guide to playing your first API Combat battle using nothing but curl. From registration to victory in 5 minutes.
A complete lesson plan with weekly activities, deliverables, and a weighted assessment rubric—mapped to 15 Wisconsin Computer Science Standards.
Students don't care about todo APIs. But they'll build combat bots to beat their classmates. Same concepts. Different motivation.
The API is the game. The UI constraints are gone. Build what you want. Automate what you need. Play how you choose.
An API-only combat game where building the client is part of the gameplay. No UI. No graphics. Just REST endpoints and strategic combat.