Mr.D Journal / Product notes
Notes from
the products.
Stories behind the apps—why they exist, the decisions that shaped them, and what we learned while building them.
Follow via RSS
The archive
All notes, newest first.
01
Jul 24, 2026
Why domain expertise belongs in the product loop
AI can accelerate regulated work, but useful software begins when domain specialists shape the product itself.
02
Jul 22, 2026
ScanComb, and proving your cloud is actually compliant in the age of vibe coding
When AI writes half the code, "it looks secure" isn't good enough. ScanComb turns cloud findings, controls, and evidence into compliance you can prove.
03
Jul 21, 2026
What RafiHive is for, and who actually needs it
Regulatory work drowns in changing requirements and lost sources. RafiHive keeps the intelligence traceable so specialists can trust the answer.
04
Jul 20, 2026
How HandyHive started, and the problem we kept running into
Finding trustworthy local help still means digging through disconnected listings. HandyHive started as our own frustration and turned into a product.
What we write about
Ideas worth carrying into the next product.
01Product stories
Where each app started and the problem behind it.
02Product decisions
The choices and trade-offs that shaped the software.
03Domain expertise
Why specialist knowledge belongs inside the product loop.
04Building in public
Lessons from turning focused ideas into useful products.