IdeaWell

Project ideas from Hacker News discussions.

Altair Basic Interpreter Source Code (1975) [pdf]

Original Article

Hacker News Discussion

📝 Discussion Summary (Click to expand)

Theme 1 – Fragility and loss of early source code
Many commenters noted how companies routinely erased code after shipment, treating it as disposable storage.
- bitwize: "The publishing company often deleted it after the game shipped, thinking it just took up space."
- reaperducer echoed this and added the costly reality of floppy disks: "Each BASF FlexyDisk cost $18 in 2026 money… That's why we printed everything out all the time; especially for archive storage."

Theme 2 – Astonishing compactness and productivity of vintage software
The discussion repeatedly marveled at how tiny and well‑thought‑out early programs were.
- joebig: "And all of it within ~4 Kbytes too!"
- piker: "These two guys were crazy productive in the 2 months they worked. Just the level of commenting shows how much thought they were able to give it during that span."
- thrownawaysz linked the idea to modern fun: "permadeath coding" would be actually fun. IF compiler error THEN erase code repository or something like this.*

Theme 3 – Contemporary practices inspired by those constraints
Developers drew parallels between historic limitations and modern workflows such as test‑driven or “delete‑on‑error” approaches.
- teddyh: "Kent Beck called this “test && commit || revert” in 2018…"
- thrownawaysz’s permadeath coding comment and the original “FILE WILL BE DELETED AFTER PRINTING” note illustrate how the mindset of temporary, expendable artifacts persists today.

🚀 Project Ideas

Generating project ideas…

Permacode

Summary

  • A cross‑platform CLI wrapper that runs your build command and, on a non‑zero exit, securely deletes the local Git repository (after creating an optional encrypted backup).
  • Core value: turns everyday coding into a “permadeath” game that forces focus, catches mistakes instantly, and encourages disciplined commits.

Details

Key Value
Target Audience Developers seeking high‑focus practice, educators, hobbyists who enjoy coding challenges
Core Feature Intercepts make, cargo, npm, etc.; on failure wipes the repo (or moves it to an encrypted vault) and reports the action
Tech Stack Rust (CLI), libgit2 for Git operations, Ring or OpenSSL for AES‑256 encryption of backups
Difficulty Medium
Monetization Hobby

Notes

  • HN users liked the idea: “permadeath coding would be actually fun. IF compiler error THEN erase code repository …”. This tool makes that concrete and safe.
  • Sparks discussion on coding discipline, could be used in live‑streamed coding challenges or classroom exercises.

CodeVault

Summary

  • A decentralized archival service that stores immutable snapshots of source code on IPFS/Filecoin, mints a proof‑of‑existence on a blockchain, and offers optional legal‑deposit “burial” with a trusted third party.
  • Core value: guarantees that even if a company deletes its repo, the code remains verifiably recoverable for decades, solving the loss of classic game source and other software heritage.

Details

Key Value
Target Audience Software companies, open‑source maintainers, digital archivists, historians
Core Feature Upload a repo → creates an immutable IPFS CID, files a Filecoin deal, records a blockchain timestamp, and provides a certificate; optional timed “bury” after which the data is sealed
Tech Stack Backend: Go or Node.js with go‑ipfs / lotus; Smart contracts: Solidity on Polygon; Frontend: React + Web3.js; Metadata stored in JSON‑LD
Difficulty High
Monetization Revenue-ready: subscription storage ($0.01/GB/mo) + minting fee ($0.05 per snapshot)

Notes

  • Commenters mourned the loss of 90s game source code and noted printing as a flawed alternative; CodeVault offers a durable, tamper‑proof solution.
  • Would generate lively HN debate about digital preservation, token incentives, and the ethics of “burying” code.

PrintCode

Summary

  • Takes source code (or a diff) and prints it as error‑correcting, high‑density QR/Data Matrix sheets on acid‑free paper, enabling reliable analog backup that can be scanned and perfectly reconstructed.
  • Core value: transforms fragile printouts into a robust, long‑term physical archive, addressing the unreliability of plain‑text printing mentioned in the thread.

Details

Key Value
Target Audience Developers, archivists, firms needing offline backups, retro‑computing enthusiasts
Core Feature Encodes files with Reed‑Solomon splits into multiple QR/Data Matrix symbols, adds pagination and metadata, outputs print‑ready PDF; companion mobile app scans and reassembles
Tech Stack Python (Reed‑Solomon via reedsolo, pylibdmtx for DataMatrix, reportlab for PDF); Scanner app: Android/iOS using ZXing core
Difficulty Medium
Monetization Hobby (open‑source CLI & PDF generator); optional premium kits (special paper, laminating) could be sold later

Notes

  • HN users reported printing everything out but found it unreliable; PrintCode adds error correction and durable media to fix that flaw.
  • Would be a neat talk‑trigger at meetups about analog vs. digital backup strategies and could be used in “code archaeology” projects.

Read Later