The latest articles on DEV Community by jim-erazeunavez (@jimerazeunavez). https://dev.to/jimerazeunavez https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4124064%2F41fb7e3a-6c36-47d0-af4f-0d0daf04e2d6.png https://dev.to/jimerazeunavez en jim-erazeunavez Mon, 14 Sep 2026 07:21:30 +0000 https://dev.to/jimerazeunavez/i-found-a-12-year-old-archive-recompiling-it-broke-the-os-the-os-was-me-447b https://dev.to/jimerazeunavez/i-found-a-12-year-old-archive-recompiling-it-broke-the-os-the-os-was-me-447b <p>I'm a dev. Last month I found an archive on an old drive.</p> <p>A 12-year-old project. No README. No tests. Just raw logs.</p> <p>I tried to recompile it. It worked. Build: Passing.</p> <p>But the system started to act weird. High CPU. Processes I didn't remember launching were running in background.</p> <p>So I did what we do: I investigated the legacy code.</p> <p>I found firewall rules: OUTBOUND: DENY<br> I found flags: response_required: NO<br> I found a lot of UNKNOWN where I expected values.</p> <p>And then I understood.</p> <p>The OS wasn't my laptop.</p> <p>The OS was me.</p> <p>The archive was a 12-year love story I never managed to close. The build was passing, but the legacy was WONTFIX.</p> <p>I documented the whole investigation. Repo is public on GitHub. Full dump is at erazeunavez.fr (in French).</p> programming sideprojects software