the rapidly dwindling sanity of valve programmers as expressed through code comments
shounicCited 3× on HN, 2021–2026
comedy · general · evergreen · 2021–2026 on HN
A short video that reads out comments from the leaked Team Fortress 2 source code to show the frustration of Valve's programmers over time.
HN cites it as an example of messy code behind successful games and of the human stories that code comments can hold.
Up next
12 mo on HNThe Problem with Time & Timezones - Computerphile
Computerphile
12 HN recommender · 2014–2026
6 mo on HNMonktoberfest 2016: Bryan Cantrill - Oral Tradition in Software Engineering
RedMonk Tech Events
6 HN recommender · 2016–2026
6 mo on HNYou Suck at Excel - Joel Spolsky (Reupload)
Cool Bug Facts
7 HN recommender · 2024–2026
5 mo on HNPure Functional Programming in Excel • Felienne Hermans • GOTO 2016
GOTO Conferences
5 HN recommender · 2017–2025
4 mo on HNThe Web That Never Was - Dylan Beattie
NDC Conferences
3 HN recommender · 2023–2026
5 mo on HNPlain Text - Dylan Beattie - NDC Copenhagen 2022
NDC Conferences
5 HN recommender · 2022–2025
5 mo on HNThe Pervert's Guide to Computer Programming Languages - SXSW
Vulk Coop
6 HN recommender · 2019–2025
4 mo on HN!!Con 2017: HDR Photography in Microsoft Excel?! by Kevin Chen
Confreaks
4 HN recommender · 2017–2025
3 mo on HNEmail Hates the Living
m
3 HN recommender · 2015–2022
3 mo on HNObsidian for Beginners: Start HERE — How to Use the Obsidian App for Notes
Linking Your Thinking with Nick Milo
3 HN recommender · 2021–2022
2 mo on HNI Have Delivered Value... But At What Cost?
KRAZAM
2 HN recommender · 2021–2024
2 mo on HNComputer Science - A Guide for the Perplexed • Joe Armstrong • GOTO 2018
GOTO Conferences
3 HN recommender · 2019–2021
3 comments from Hacker News
I've been coding by hand for nearly 20 years. I don't get any rush from generating code with agents. Most of the time I just feel loss. Coding to me has always been the work of a craftsman. I spent years learning syntax, studying APIs, and generally becoming an expert in a language I could then use to exactly express myself. My code became my way of of telling a story. I picked that language not only because it was the right tool for the job, but because I liked the community, I liked the direction of the tool, and I liked writing it. Agents obliterate all of that. Before, source code was like exploring a canyon. Each function, loop, and nested brackets was someone's choice. There was an implicit story to follow. Agentic code is that valley after the glaciers have retreated. A good illustration of what I'm afraid of losing is in those videos cataloging the [the rapidly dwindling sanity of valve programmers as expressed through code comments]( ▶ this video ). When AI generates your code, you lose that context. You lose that human connection to code that I care so much about. Unfortunately, I don't think the human touch was as high-of-value to other developers as I previously thought. I've realized that for most developers, it was never about the journey, it was about getting to the destination as quickly as possible. We were infected with a plague of idea-guys and didn't even know it. That's okay. There are a billion things in the world where what was once the sole dominion of craf
Like the author states, the "written in Rust" bonus many projects get does not apply to games. Most of the games I consider to be the most fun are built on an absolute rats nest dumpster fire of code (see: ▶ this video ). Sometimes bugs even expand game mechanics and make them more fun and expressive. That being said I'll definitely check out Unrelaxing Quacks, it looks great.
Valve's development practices are apparently good for a chuckle. ▶ this video The devs don't seem like they have enough time to deal with the code they have to write, let alone respond to security issues. (not their fault, of course)