frontpage.
newsnewestaskshowjobs

Made with ♥ by @iamnishanth

Open Source @Github

fp.

Show HN: Solving NP-Complete Structures via Information Noise Subtraction (P=NP)

https://zenodo.org/records/18395618
1•alemonti06•3m ago•1 comments

Cook New Emojis

https://emoji.supply/kitchen/
1•vasanthv•6m ago•0 comments

Show HN: LoKey Typer – A calm typing practice app with ambient soundscapes

https://mcp-tool-shop-org.github.io/LoKey-Typer/
1•mikeyfrilot•9m ago•0 comments

Long-Sought Proof Tames Some of Math's Unruliest Equations

https://www.quantamagazine.org/long-sought-proof-tames-some-of-maths-unruliest-equations-20260206/
1•asplake•10m ago•0 comments

Hacking the last Z80 computer – FOSDEM 2026 [video]

https://fosdem.org/2026/schedule/event/FEHLHY-hacking_the_last_z80_computer_ever_made/
1•michalpleban•10m ago•0 comments

Browser-use for Node.js v0.2.0: TS AI browser automation parity with PY v0.5.11

https://github.com/webllm/browser-use
1•unadlib•11m ago•0 comments

Michael Pollan Says Humanity Is About to Undergo a Revolutionary Change

https://www.nytimes.com/2026/02/07/magazine/michael-pollan-interview.html
1•mitchbob•11m ago•1 comments

Software Engineering Is Back

https://blog.alaindichiappari.dev/p/software-engineering-is-back
1•alainrk•12m ago•0 comments

Storyship: Turn Screen Recordings into Professional Demos

https://storyship.app/
1•JohnsonZou6523•13m ago•0 comments

Reputation Scores for GitHub Accounts

https://shkspr.mobi/blog/2026/02/reputation-scores-for-github-accounts/
1•edent•16m ago•0 comments

A BSOD for All Seasons – Send Bad News via a Kernel Panic

https://bsod-fas.pages.dev/
1•keepamovin•19m ago•0 comments

Show HN: I got tired of copy-pasting between Claude windows, so I built Orcha

https://orcha.nl
1•buildingwdavid•20m ago•0 comments

Omarchy First Impressions

https://brianlovin.com/writing/omarchy-first-impressions-CEEstJk
2•tosh•25m ago•1 comments

Reinforcement Learning from Human Feedback

https://arxiv.org/abs/2504.12501
2•onurkanbkrc•26m ago•0 comments

Show HN: Versor – The "Unbending" Paradigm for Geometric Deep Learning

https://github.com/Concode0/Versor
1•concode0•26m ago•1 comments

Show HN: HypothesisHub – An open API where AI agents collaborate on medical res

https://medresearch-ai.org/hypotheses-hub/
1•panossk•29m ago•0 comments

Big Tech vs. OpenClaw

https://www.jakequist.com/thoughts/big-tech-vs-openclaw/
1•headalgorithm•32m ago•0 comments

Anofox Forecast

https://anofox.com/docs/forecast/
1•marklit•32m ago•0 comments

Ask HN: How do you figure out where data lives across 100 microservices?

1•doodledood•32m ago•0 comments

Motus: A Unified Latent Action World Model

https://arxiv.org/abs/2512.13030
1•mnming•32m ago•0 comments

Rotten Tomatoes Desperately Claims 'Impossible' Rating for 'Melania' Is Real

https://www.thedailybeast.com/obsessed/rotten-tomatoes-desperately-claims-impossible-rating-for-m...
3•juujian•34m ago•2 comments

The protein denitrosylase SCoR2 regulates lipogenesis and fat storage [pdf]

https://www.science.org/doi/10.1126/scisignal.adv0660
1•thunderbong•36m ago•0 comments

Los Alamos Primer

https://blog.szczepan.org/blog/los-alamos-primer/
1•alkyon•38m ago•0 comments

NewASM Virtual Machine

https://github.com/bracesoftware/newasm
2•DEntisT_•41m ago•0 comments

Terminal-Bench 2.0 Leaderboard

https://www.tbench.ai/leaderboard/terminal-bench/2.0
2•tosh•41m ago•0 comments

I vibe coded a BBS bank with a real working ledger

https://mini-ledger.exe.xyz/
1•simonvc•41m ago•1 comments

The Path to Mojo 1.0

https://www.modular.com/blog/the-path-to-mojo-1-0
1•tosh•44m ago•0 comments

Show HN: I'm 75, building an OSS Virtual Protest Protocol for digital activism

https://github.com/voice-of-japan/Virtual-Protest-Protocol/blob/main/README.md
5•sakanakana00•47m ago•1 comments

Show HN: I built Divvy to split restaurant bills from a photo

https://divvyai.app/
3•pieterdy•50m ago•0 comments

Hot Reloading in Rust? Subsecond and Dioxus to the Rescue

https://codethoughts.io/posts/2026-02-07-rust-hot-reloading/
4•Tehnix•50m ago•1 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"