Monday's plan vs Friday's reality. Sometimes you ship less — and you say so anyway.
Planned
- process library: 100+ definitions (chrome.exe, python.exe…)
- add timestamps to hck_GPT messages
- write 1–2 articles
Shipped
- JSON structure ready (empty, but the framework works)
- 1 article published — the EventDetector deep-dive (Medium + dev.to)
Scarred
- no 100+ processes yet
- no timestamps yet
- way behind plan
Week 1 at Żabka hit different than expected. By evening I was too tired to think, let alone code process definitions. Turns out writing "chrome.exe — Google Chrome browser, RAM-heavy with many tabs" a hundred times requires brain cells I didn't have left after 9-hour retail shifts.
The lesson: ambitious weekly plans assume consistent energy. Week 1 of a new job has zero consistent energy. I underestimated the adaptation cost. Rookie mistake.
Forward: Easter weekend, days off, max coding mode. Process library getting filled, timestamps getting added. Sometimes reality hits harder — but you don't stop. Monday sets the bar; Friday shows what actually happened. Both matter.
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.