The Man Who Got Himself back
PC Workman 1.8.0 is the release where my system monitor finally learned to remember your machine. It's also the story of the year I spent getting mine back.
I've stopped being able to tell those two apart.
I had to shout at a man that I'm not a terrorist.
SNF (Stichting Normering Flexwonen)
was the only thing that stopped him from putting me on the street that night, out of the apartment the work agency had housed me in for four months. Building was certified. I knew my rights.
He was gambling that I didn't.
So I stood in a corridor somewhere in the Netherlands and screamed the single most absurd sentence of my life, three days before Christmas.
In a foreign language.
For weeks the people at that job had smiled at me.
Then, wearing the same smile:
"You didn't pass the trial. Tomorrow, goodbye and out of the apartment."
The 22nd of December.
My suitcases were by the door before I'd finished understanding the sentence. Two dogs waiting for me in another country. A laptop that climbs to 94°C if I ask it to think too hard. Maybe a month of money left.
I'm telling you this first because that corridor is where this project was made, and four nights ago, at three in the morning, it's still where it's being made.
PC Workman, the thing I shipped this week, was written in conditions like that, and it is still being written in conditions like that.
So yes, this is a release note. 1.8.0 is out:
the version where my monitor finally remembers your machine instead of meeting it like a stranger every time you open it.
But I'd be lying if I sold it to you as software and stopped there.
Because the twelve months I spent teaching a program to remember are the same twelve months I spent getting myself back.
And here's about I didn't expect to be able to write down:
somewhere in that year, I found the guy who went missing.
He'd been in the code the whole time.
The number you never see cross a line
My father died when I was seventeen.
I didn't break that week.
I broke slowly, over the next two or three years, and that's something no one warns you about:
there's no moment. No threshold you catch yourself crossing.
It's a power rail sagging: 12 volts becomes 11.9, becomes 11.8, and every reading is still "within spec" so nothing alarms, and then one day you look at the number and it's just wrong, and you have no idea when that happened.
I went through technical school on fumes. INF.02 on the paper, nothing behind it. And somewhere around 2022, after school handed me the entire weight of being an adult all at once, I gave up on myself. Quietly. The way almost everyone does it.
The part people will either love or refuse to print:
it was AI that helped me find the exact day I quit.
Bounced between agencies whose names I never learned,
I started talking to a machine the way you'd talk to the one person who never gets tired of you, and it helped me locate the moment, the decision, the sag.
And the second I could see it, I could refuse it. That's the whole thesis, honestly. You cannot fix a number you never learned to measure.
So I made a decision that looks stupid typed out and felt like survival at 3 a.m.: I will not let this grind me into one more used-up man it spits out the far end. I'll work while I have strength. I'll learn one thing a day. I'll build out loud, in public, so I can't quietly vanish. And I will not, at thirty, look in a mirror and hate the kid who stopped trying at twenty-two.
Then I opened my editor.
A monitor that remembers you
PC Workman tells you why your PC is slow, not just that it is. It learns your machine — your temperatures by workload, your voltage patterns, the games you actually play — and it talks to you through an offline AI assistant I wrote called hck_GPT. 84 intents, no cloud, no API key, all of it running on your own metal.
There's one-click optimization, ghost-driver detection for hardware you ripped out years ago, an in-game overlay that starts empty and shows only what you choose, and a small antivirus that checks who really signed a process instead of trusting the name.
The 1.8.0 receipts: 84 intents, 373 known processes, 40+ games it greets by name, 21/21 tests green, ~790 downloads across SourceForge and GitHub, 61 stars — and twelve dead projects buried behind it.
But the headline of 1.8.0 is the only part I actually lose sleep over. Memory.
Every monitor on earth forgets you the second you close it.
HWiNFO, Afterburner, open them tomorrow and they'll draw your 78°C against the exact same line they draw for every machine that has ever existed.
I couldn't live with that.
The most useful number a monitor can give you isn't the temperature.
It's whether this temperature is normal for you, and to answer that, the thing has to remember.
So every reading falls into one of five workload buckets, and each keeps its own learned normal:
def classify(self, cpu_load, gpu_load=0.0):
"""Return the workload bucket for the given CPU / GPU utilisation."""
if (gpu_load or 0.0) >= 60.0: return "gaming"
cl = cpu_load or 0.0
if cl < 15.0: return "idle"
if cl < 40.0: return "light"
if cl < 70.0: return "medium"
return "heavy"
82°C while you game: fine.
82°C sitting idle: something's wrong.
Same number, opposite verdict, judged against your own past instead of a spec line.
And it does not forget. I tore out the old 14-day window and rebuilt it as a Welford accumulator: three numbers per workload, a running count,
a mean, and a thing called M2 — folded forward, never recomputed.
def _welford_add(acc, x):
"""Fold one sample into a running accumulator (Welford, 1962)."""
n = acc["n"] + 1
delta = x - acc["mean"]
mean = acc["mean"] + delta / n
acc["n"] = n
acc["mean"] = mean
acc["M2"] = acc["M2"] + delta * (x - mean)
It keeps learning for the entire life of the install, and the learned shape survives even after the raw data gets pruned at ninety days.
Detail rolls off.
Shape of your machine stays.
That's the whole memory.
Statistics from the 1960s, babysitting your power supply
Voltages got the oldest math in the project.
Spec says your 12V rail is fine anywhere between 11.4 and 12.6. Technically true, practically uselessm a healthy supply doesn't roam that whole band, but holds tight, around 11.95 to 12.05.
So instead of the spec, PC Workman learns the median and spread of your rail and runs Nelson rules from 1984 on top of it, hunting the slow sag the threshold will never catch.
It scores every reading against your own history with a modified z-score, median and MAD, not mean and σ, because one spike drags an average up and lets the next one sail through:
M = 0.6745 × (x − median) / MAD
A drift to 11.7V is invisible to the spec and screams against your own history. Early warning, months before anything actually dies.
You already know why I had to build that. I am the rail that sagged for three years inside spec while everyone, me included swore nothing was wrong. I built the alarm I never had.
Sixty-year-old statistics babysitting a power supply.
Boring, predictable, and that is exactly why I trust them.
Statistics don't hallucinate. People do. People looked me in the eye at 19 PLN an hour and said, "just try harder, the rate will get better."
It never got better. Math, at least, never lied to me.
Written after the shift
I need you to see where this actually gets made, because it changes how you read everything above.
PC Workman does not get built in a clean bedroom with a mechanical keyboard and a ring light. It gets built after I weld.
Hot air, a gun, melting plastic grates back together in a workshop, and then I go home, open a laptop from 2014, and write a Welford accumulator on it.
That contrast used to embarrass me.
It doesn't anymore, because the welding taught me the one thing the memory engine needed. You don't get an eye for hot metal from a manual.
It accumulates, cherry red, straw, blue that means you already gone too far.
Nobody hands it to you. You earn it by burning enough of it until the knowledge in your hands is yours and not the chart's.
That's the entire philosophy of the learning engine, and I learned it with a heat gun before I ever wrote it in Python.
Fear changed shape
Here's what I only understood this week, and have never written before.
For a year the fear was simple:
I'm scared of disappearing, so I build. Commit something, watch a progress bar move, prove I still exist. That fear is loud but clean.
When you've got nothing, you've got nothing to lose, and that turns out to be its own brutal kind of freedom.
Then something I made hit #1 trending on HackerNoon and held it there for two days.
I have a small, real community now, people who spend eight hours stress-testing my releases and then come back.
And the fear quietly mutated into something heavier:
now I have something I can lose.
It took me off the board for a week.
I cried for three days. Not from joy.
From a flavor of dread I didn't have a word for. It was a fluke.
I'll lose it all. Maybe it only works once. Impostor syndrome, except impostor syndrome while you're broke and welding plastic to eat is a different animal entirely.
It rides shotgun with every single small win, every day.
But under the dread was the truest sentence I own, and I'm almost proud of it: I went from trying to gain to having something to protect.
The second one is a step higher up the stairs even when he's the one sitting on them, crying.
Three in the morning
Monday I shipped 1.8.0.
It was supposed to go out four days earlier.
I kept pushing it back because I kept finding more, more bugs to kill, more to test, more of the machine to teach, more reasons not to put my name on something half-true.
In four days I did close to two weeks of work.
I clicked publish at three in the morning.
Then I lay down to sleep, and from three until twenty past four I stared at the ceiling and asked the only question that ever really comes for me at that hour: does any of this mean anything.
I get that question every two to four days. Always at night.
And here's the thing I've learned to trust like a law of physics:
it lasts about an hour. Sometimes two, sometimes three. And then I beat it, all the way, not halfway. And the motivation comes back whole, like nothing happened.
You don't argue with weather. You survive the hour, and you wait for the part where time and stubbornness pay you back.
At 4:20 I stopped asking. By nine I was writing this.
The man who got himself back
I wanted to title this The Man Who Got Himself Back. In Polish, my language — "Człowiek odzyskał siebie." It's a beautiful title. It's also a lie, and I'd rather hand you the truth, because it's the one thing on this entire page I'm actually sure of.
You don't get yourself back once. There's no ceremony,
though one did land in my hands the same Monday I shipped this, a Google one:
Skills of Tomorrow 3.0 AI, five weeks that felt exactly like the accumulator, not knowledge downloaded, knowledge folded in, slowly, never recomputed.
But certificate isn't the moment. Moment is smaller, and it repeats.
You get yourself back at twenty past four in the morning, when the question comes and you outlast it one more time.
You get yourself back the next night the laptop boots warm and you write one more function instead of closing the lid.
My monitor learns for the life of the install.
I learn for the life of mine. This grind is twelve months old, it has not ended, and it is not going to, and I've finally understood that this is not the tragedy of the story. It's the proof of it.
A finished man has nothing left to recover.
I get to keep recovering. That's a pulse.
I get myself back. Every morning.
Not yet not today. I'm still here.
Find me (and maybe the first coffee?)
PC Workman 1.8.0 is free and open source (MIT), one ZIP, no installer, no account, runs locally on your machine.
⭐ Star / download: github.com/HuckleR2003/PC_Workman_HCK
Site: pcworkman.dev
Coffee: buycoffee.to/hcklabs
Everything (LinkedIn - X - Dev.to):
linktr.ee/marcin_firmuga
Polish version: pcworkman.dev/blog/the-man-who-got-himself-back_pl
About the author
I'm Marcin Firmuga, solo developer and founder of HCK_Labs.
I created PC Workman, an open-source, AI-powered PC resource monitor that learns your PC's natural behavior over time, spikes, voltages, temperatures, usage built entirely from scratch on dying hardware during warehouse shifts in the Netherlands.
Before this:
game translations, PC-technician internships, warehouse operations in multiple countries, and countless failed projects I never finished.
But this one? This one stuck. Twelve months of code. Four complete UI rebuilds. 26,000 lines deleted, ~50,000 total. 3 a.m. all-nighters. Energy drinks and toast. And my own hck_GPT AI, built over months to give PC Workman a brain and a heart.
And finally, an app I wouldn't close in five seconds. That's the difference between building and shipping.
Built solo and in public by Marcin "HCK" Firmuga - 22, Radom, Poland. After the welding shift, on a 2014 laptop, in the hour between the night breakdowns. GitHub: HuckleR2003 · pcworkman.dev. Still shipping.
Top comments (0)