frontpage.
newsnewestaskshowjobs

Made with ♥ by @iamnishanth

Open Source @Github

fp.

Start all of your commands with a comma

https://rhodesmill.org/brandon/2009/commands-with-comma/
53•theblazehen•2d ago•10 comments

OpenCiv3: Open-source, cross-platform reimagining of Civilization III

https://openciv3.org/
636•klaussilveira•13h ago•188 comments

The Waymo World Model

https://waymo.com/blog/2026/02/the-waymo-world-model-a-new-frontier-for-autonomous-driving-simula...
935•xnx•18h ago•549 comments

What Is Ruliology?

https://writings.stephenwolfram.com/2026/01/what-is-ruliology/
35•helloplanets•4d ago•30 comments

How we made geo joins 400× faster with H3 indexes

https://floedb.ai/blog/how-we-made-geo-joins-400-faster-with-h3-indexes
113•matheusalmeida•1d ago•28 comments

Jeffrey Snover: "Welcome to the Room"

https://www.jsnover.com/blog/2026/02/01/welcome-to-the-room/
13•kaonwarb•3d ago•11 comments

Unseen Footage of Atari Battlezone Arcade Cabinet Production

https://arcadeblogger.com/2026/02/02/unseen-footage-of-atari-battlezone-cabinet-production/
45•videotopia•4d ago•1 comments

Show HN: Look Ma, No Linux: Shell, App Installer, Vi, Cc on ESP32-S3 / BreezyBox

https://github.com/valdanylchuk/breezydemo
222•isitcontent•13h ago•25 comments

Monty: A minimal, secure Python interpreter written in Rust for use by AI

https://github.com/pydantic/monty
214•dmpetrov•13h ago•106 comments

Show HN: I spent 4 years building a UI design tool with only the features I use

https://vecti.com
323•vecti•15h ago•142 comments

Sheldon Brown's Bicycle Technical Info

https://www.sheldonbrown.com/
373•ostacke•19h ago•94 comments

Microsoft open-sources LiteBox, a security-focused library OS

https://github.com/microsoft/litebox
359•aktau•19h ago•181 comments

Hackers (1995) Animated Experience

https://hackers-1995.vercel.app/
478•todsacerdoti•21h ago•237 comments

Show HN: If you lose your memory, how to regain access to your computer?

https://eljojo.github.io/rememory/
278•eljojo•16h ago•165 comments

An Update on Heroku

https://www.heroku.com/blog/an-update-on-heroku/
407•lstoll•19h ago•273 comments

Dark Alley Mathematics

https://blog.szczepan.org/blog/three-points/
85•quibono•4d ago•21 comments

PC Floppy Copy Protection: Vault Prolok

https://martypc.blogspot.com/2024/09/pc-floppy-copy-protection-vault-prolok.html
57•kmm•5d ago•4 comments

Delimited Continuations vs. Lwt for Threads

https://mirageos.org/blog/delimcc-vs-lwt
26•romes•4d ago•3 comments

Vocal Guide – belt sing without killing yourself

https://jesperordrup.github.io/vocal-guide/
16•jesperordrup•3h ago•10 comments

How to effectively write quality code with AI

https://heidenstedt.org/posts/2026/how-to-effectively-write-quality-code-with-ai/
245•i5heu•16h ago•193 comments

Was Benoit Mandelbrot a hedgehog or a fox?

https://arxiv.org/abs/2602.01122
14•bikenaga•3d ago•2 comments

Introducing the Developer Knowledge API and MCP Server

https://developers.googleblog.com/introducing-the-developer-knowledge-api-and-mcp-server/
54•gfortaine•11h ago•22 comments

I spent 5 years in DevOps – Solutions engineering gave me what I was missing

https://infisical.com/blog/devops-to-solutions-engineering
143•vmatsiiako•18h ago•64 comments

Understanding Neural Network, Visually

https://visualrambling.space/neural-network/
284•surprisetalk•3d ago•38 comments

I now assume that all ads on Apple news are scams

https://kirkville.com/i-now-assume-that-all-ads-on-apple-news-are-scams/
1061•cdrnsf•22h ago•438 comments

Why I Joined OpenAI

https://www.brendangregg.com/blog/2026-02-07/why-i-joined-openai.html
136•SerCe•9h ago•124 comments

Learning from context is harder than we thought

https://hy.tencent.com/research/100025?langVersion=en
178•limoce•3d ago•96 comments

Show HN: R3forth, a ColorForth-inspired language with a tiny VM

https://github.com/phreda4/r3
70•phreda4•12h ago•14 comments

Female Asian Elephant Calf Born at the Smithsonian National Zoo

https://www.si.edu/newsdesk/releases/female-asian-elephant-calf-born-smithsonians-national-zoo-an...
28•gmays•8h ago•11 comments

FORTH? Really!?

https://rescrv.net/w/2026/02/06/associative
63•rescrv•21h ago•23 comments
Open in hackernews

What a Programmer Does (1967) [pdf]

http://archive.computerhistory.org/resources/text/Knuth_Don_X4100/PDF_index/k-9-pdf/k-9-u2769-1-Baker-What-Programmer-Does.pdf
100•nz•3w ago

Comments

svat•3w ago
What does Knuth mean by

> I particularly like his definitinon of a bad programmer. (My personal record is about 12 years.)

here?

tjr•3w ago
The article describes a bad programmer as one whose programs “die young”. I would guess that Knuth is saying is that the longest one of his programs lived (was used?) for 12 years?

If that is what he meant, I presume this remark was written well in the past, as TeX has lasted way more than 12 years.

bdunks•3w ago
That makes sense. His cover letter is dated 1974, and TeX was released 1978.
syncsynchalt•3w ago
The note is actually from Chuck Baker, the editor of that issue of Datamation.

You're not alone in assuming DEK wrote the note, a lot of people seem to attribute it to Knuth.

svat•3w ago
I see. I was talking about not the article itself, but this handwritten note on the front page:

> This article from Datamation is by someone from ADR - the name might be Moore. (It wasn't meant to be anonymous; that was accidental). A lot of people who knew me thought I wrote it. I wish I had!

> I particularly like his definition of a bad programmer. (My personal record is about 12 years.)

The scan comes from Knuth's personal collection scanned by the Computer History Museum. Many of the documents have similar notes by Knuth, so I assumed this was by him too. Though on closer look, I'm not so sure the handwriting is the same. (It would be ironic if a note about misattribution gets misattributed.) How do you know the note is by Chuck Baker?

grener75•3w ago
It was probably written by William H. Moore of ADR.
syncsynchalt•2w ago
Thank you for tracking this down! I made some half-hearted stabs at who it might be but wasn't even sure I was reading the "ADR" right.
svat•3w ago
Answering the question: the handwritten note is indeed by Chuck Baker (see https://news.ycombinator.com/item?id=12569853) — matches the handwriting at https://archive.computerhistory.org/resources/text/Knuth_Don...

It's interesting that the editor didn't know the author of one of the articles in their magazine!

aaronblohowiak•3w ago
If you liked this, you may like my favorite paper https://pages.cs.wisc.edu/~remzi/Naur.pdf
perrygeo•3w ago
It's remarkable how these papers show a deep understanding of programming 50 years ago. Even with anemic hardware, the limit is always in the programmers brain - as uncomfortable as that is to admit. Half a century of new tech and AI and the cloud etc, we still hit "terminal trauma" fairly quickly in the development cycle, almost like clockwork. All the tools and technical tricks don't seem to matter vs. our ability to hold the application in our heads.
dang•3w ago
One past discussion:

What a Programmer Does (1967) [pdf] - https://news.ycombinator.com/item?id=12568863 - Sept 2016 (45 comments)

(Reposts are fine after a year or so; links to past threads are just to satisfy extra-curious readers)

ontouchstart•3w ago
We might want to repost it every decade.
ontouchstart•3w ago
https://archive.computerhistory.org/resources/text/Knuth_Don...

Bookmark here for me to read in 2036.

devhouse•3w ago
Will it now instead of “write code for humans”, become “write Prompts for humans” with AI?
whntheduvscry•3w ago
> The terminal trauma of a program occurs when it is challenged by entropy beyond its capacity to adjust.

This seems true.

In my experience, these things that happened to kill programs could be considered entropy:

- New (e.g. hardware / software / code / people / focus)

- Money (e.g. actual or perceived infusion of it / actual or perceived lack of it / focus changed)

- Loss (e.g. someone or something left / was injured / died / was destroyed / was deleted / was corrupted)

And I think that if you have a system that contains risk due to entropy, then even a planned event resulting in success is entropic, e.g.:

- I plan a sunset for X software.

- There is risk of an asteroid or sudden epidemic that would thwart that plan.

- The “dice are rolled”, and the sunset happens because the asteroid and epidemic didn’t happen.

- Therefore, the planned sunset occurred due to less than 100% chance. This is still entropic.

A_Duck•3w ago
The 'Aerospace Corporation' job ad!

"These are excellent opportunities for men ... An equal opportunity employer"