Monday Grind Blueprint #1: Timestamp Everything + a 100-Process Library

By Marcin Firmuga·2026-03-30·2 min read·Monday Grind Blueprint #1

Week one of building PC_Workman in public. Here's the plan.

This week I'm tackling something that's bugged me since day one: when hck_GPT tells you "Chrome ate 6 GB RAM three hours ago" — which three hours? And what even is msedge.exe?

Goal 1 — timestamp everything

Every hck_GPT message gets a timestamp. Spike detected at 14:37. Report generated at 09:15. No more "recently" or "a while ago" — exact times.

Goal 2 — a process library (100+ definitions)

A JSON database of common processes: what they are ("chrome.exe — Google Chrome browser"), who made them ("Google LLC"), what they do ("web browsing, can eat RAM with too many tabs"). Hover over any process in hck_GPT for an instant tooltip — no more Googling "what is svchost.exe?"

Goal 3 — write it down

Publishing 1–2 articles this week: recent updates (Stats Engine v2, EventDetector) and the git backup lessons (lost 130 commits, recovered 90).

Why this matters: users don't need more data — they need context. That's the difference between "CPU: 87%" and "CPU spiked to 87% at 14:37 because Chrome opened 50 tabs."

Building v1.6.8 → v2.0. Monday Grind Blueprint every week — real plans, not vague goals.

BuildInPublicPythonIndieHacker

This is the project behind the post. PC Workman is a free, open-source Windows system monitor with an offline AI assistant - everything described here is real, shipped code. Download it or read the source.

Marcin Firmuga

Solo developer · HCK_Labs · building PC Workman in public

Every edition is written from that week's real commits. Newest posts premiere on LinkedIn - the archive lives here. More about me: my story.

GitHub LinkedIn X dev.to Buy me a coffee ☕