Every developer blog starts with a post promising consistency, and most of those blogs have exactly one post. So instead of promising, I'll just explain the system.
Why write at all
I spend my weeks split between three worlds: CS coursework at St. John's, AI/ML research in healthcare informatics at the Bukhari Lab, and my own projects. The context-switching is real — one day it's process schedulers, the next it's model evaluation on health data, the next it's debugging a Next.js build.
Writing is how I'll force those worlds to talk to each other. If I can't explain a thing simply by Friday, I didn't understand it on Monday.
What to expect
- Build logs — what I shipped, what broke, and the fix I wish I'd found on page one of my search results.
- Research notes — what working in a healthcare informatics lab actually looks like as an undergrad (spoiler: a lot of data cleaning).
- Course distillations — the one insight per class that was worth the tuition.
The cadence
One post a week. Some will be short. The newsletter version comes with an AI-generated summary, so you can decide in ten seconds whether the full post is worth your time — that feels like the polite way to run a mailing list.
See you next week. 🚀