I Tried Fixing One Chart Bug. Three Weeks Later I Had Rebuilt My Entire AI Monitoring Engine. PC Workman 1.6.8The most dangerous sentence in software development is: "This should only take two days." That’s exactly how PC Workman v1.6.8 started. One tester asked me a completely reasonable question: "Can I 2May 16 · 7 min readhck.hashnode.dev
I Spent 6 Months Building a Python App Nobody Could RunFor 6 months, PC Workman only existed on GitHub. The code worked.The architecture worked.The monitoring engine worked. But none of that mattered. Because nobody outside developer circles is going to c2May 16 · 6 min readhck.hashnode.dev
How I Built an AI Manual Assistant Between Warehouse Shifts (and Why It Told Me to Put Charcoal in a Washing Machine)The physical world is still stuck in the 90s. I spend my days picking orders in a warehouse — heavy boxes, forklifts, and dust everywhere. But my nights belong to my laptop. For months I kept asking m3May 10 · 3 min readhck.hashnode.dev
The Night I Stopped Building For Myself (And Why It Saved My Project)The Night I Stopped Building For Myself (And Why It Saved My Project)"If I were a real user, I’d quit this in five seconds." That single thought hit me harder than my 2014 laptop screaming at 94°C.Bec3May 10 · 3 min readhck.hashnode.dev
Sigstore Made Easy: How I Prove PC_Workman Is Actually From MeHere’s the uncomfortable truth about open source: Anyone can say they built something. And when users download your .exe…They’re not just downloading code. They’re trusting that it actually came fro3Apr 7 · 4 min readhck.hashnode.dev