matbanik

Published May 22, 2026 on matbanik.info Manuel Gil's Windows Update reset script crossed half a million downloads before he archived it in March 2023. The Dev-C++ successor — Reset-Windows-Update-Tool, 513 stars on GitHub — followed it into the archive on January 16, 2026. For years, these were the tools sysadmins reached for when Microsoft's troubleshooter shrugged and said "we couldn't identify the problem." They're gone now. And nothing replaced them. Search "reset Windows Update" today and you'll find plenty of consumer guides. Screenshots of Settings panels. "Click Troubleshoot, then Additional troubleshooters." The irony: that troubleshooter is itself being deprecated with the MSDT retirement. Microsoft is sunsetting its own fix-it tool. For MSP technicians managing hundreds of endpoints, the gap is worse. You need something that runs silently through your RMM. Something that won't obliterate the Intune ring configurat...

Published May 20, 2026 on matbanik.info You paid somewhere between $300 and $500 for whole genome sequencing. Maybe Nebula, maybe Dante, maybe one of the newer providers that keep undercutting each other. You got a folder. Inside that folder: a VCF file with 4.86 million rows of variant data and a dashboard that shows you maybe 1% of what's in there. The dashboard answers their questions. Ancestry breakdown. A handful of trait associations. Maybe a carrier screening if you're lucky. But your questions — the ones that actually matter to you — don't have a button. "What are my CYP enzyme metabolizer phenotypes?" No button. "Which variants did I inherit from my father versus my mother?" Definitely no button. "What does ClinVar say about that variant my doctor flagged last week?" Not even close. This post is about closing that gap. I'll show why it exists, what it looks like when it's gone, and how to set it up yourself — local...

Published May 13, 2026 on matbanik.info I started building a platform with AI agents writing most of the code. Two different models. Eleven project phases. Over 1,500 tests. More than 200 features shipped. Then one morning I opened my own repository and couldn't trace the execution path through a service I'd supposedly built. The code was clean. The tests passed. The architecture followed every pattern I'd specified. But when I tried to explain why a particular order validation happened before portfolio sync instead of after, I just... stared at the screen. The logic was there. My understanding wasn't. That's not a horror story. It's just what happens when you adopt a tool without vetting it the way you'd vet any other dependency in your stack. I started asking different questions — the kind you'd ask before adding something critical to a production system. Here are four that keep surfacing. What Changed About the Work — and What Didn...