★ New · The complete record
Fourteen months, four jobs, one application, and still no job in software
Every month, with the real dates and the real numbers. A warehouse in the Netherlands, being fired three days before Christmas, a convenience store, welding plastic, a taxi, and 23 released versions in between. Including the months where nothing worked.
Read the timeline → ★ New · Now on the Microsoft StoreFrom a Warehouse Floor to the Microsoft Store
A year ago I scanned barcodes and coded every night because I was afraid of disappearing. Today PC Workman is on the Microsoft Store — permanently. The whole story, and the math underneath it.
Read the milestone → ★ Featured · The story behind 1.8.0The Man Who Got Himself Back
Fired three days before Christmas. A 2014 laptop at 94°C. Built after the welding shift. I taught a program to remember your machine — and spent the same year getting myself back. The release note and the confession.
Read the story →Prefer the technical release notes? → 1.8.0 — The Release That Remembers
Scaling Laws
Behind the game dev scene
I sat on a finished build for three weeks because I was afraid of it
Twenty-nine days from the first commit to a public build, written down while it was still uncomfortable. What the fear actually was, what shipping cost, and the first numbers back.
Read it ->What USS cannot do in Unity UI Toolkit
No gradients, no arcs, no masks, no positional selectors. What breaks, and what to use instead.
The feature that is finished, tested, and impossible to reach
A green test suite proves a function works. It proves nothing about whether anything calls it.
42 save format changes, and not one broken campaign
One step per version, old shapes kept verbatim, and every reconstruction declared rather than hidden.
What an AI accelerator is worth one, two and three years later
Eight generations, launch price against cost per petaflop, and the residual value table.
Scaling Laws is an AI company tycoon built by Marcin Firmuga under HCK Labs. Version 0.4.0 is free for Windows. The game page has the download, and How Scaling Laws works opens the machinery.
Grind Blueprint
The week's plan, announced publicly before the work starts. A commitment you can't quietly walk back.
Open series -> WednesdayCode Autopsy
One bug or feature on the table: root cause, dead ends, the actual fix. Code included.
Open series -> FridayShipped & Scarred
Monday's plan vs Friday's reality. What shipped, what died, what scars remain.
Open series ->Grind Blueprint
I Do Not Have a Job. My CV Keeps Coming Back. I Am 22.
Fifteen months from a warehouse to a Microsoft Store app and a game at 0.4.0. Everything earned so far: 70 zł. Maybe building more was the wrong question.
#24One Evening, a Pen and a Piece of Paper Found Four Things 1115 Tests Had Not
Samanta played Scaling Laws for one evening and took notes. A paragraph that never reached the game, music that stepped at the seam, and a test that caught my fix.
#23Most Developers Have Never Seen Their Own Application
Six hours before release, Scaling Laws opened with its title bar off the screen and its bottom bar behind the taskbar. Why the editor could never show me that.
Full series →Code Autopsy
I Opened Google Search Console to Check Which of My Guides People Actually Find
Poland sends 33 clicks in six months. The Netherlands, where I scanned barcodes eighteen months ago, sends 32 and has the highest click rate on the list.
#24Someone Found My Game Through Google’s AI
A player found Scaling Laws through Google’s AI, played it and sent five things that were wrong, including an idea I had never written down: cancel anything.
#23Nothing in Your Build Fails When Your README Starts Lying
My README said a coasting company goes insolvent in three years. The harness says the fifth. How one unmeasured number lived for three weeks across three websites.
Full series →Shipped & Scarred
I Finished It Two Days Early, and I Did Not Choose a Single Thing That Is in It
A stranger found the game, played it and sent four things that were wrong. I gave him a date. Three with a date are finished. The one without has not moved.
#23Somebody Arrived on My Site With a Broken SSD and Left With a Game About Running an AI Lab
23 troubleshooting guides written in summer. By autumn Google shows the site 200 times a day, and twenty people who came about a failing disk downloaded the game.
#22On Wednesday I Wrote About Not Hearing Back. By Thursday Two More People Had Put My Name Forward.
Fourteen months of building did not get me a referral. Admitting I had been waiting did. Plus the tutorial bug my partner found by reading slower than every test.
Full series →From warehouse night shifts to a homemade AI
A 2014 laptop at 94°C, a firing on December 22nd, and the monitor that came out of it.
Who builds PC Workman
Marcin Firmuga — solo developer, HCK_Labs. The person behind every commit.