frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

Anthropic employee claims general proof of the Riemann Hypothesis [pdf]

https://alpo.ge/remark.pdf
260•iamronaldo•50m ago•83 comments

If you can't explain something in simple terms, you don't understand it (2017)

https://kottke.org/17/06/if-you-cant-explain-something-in-simple-terms-you-dont-understand-it
276•sammatilda•5h ago•163 comments

Frostbite: A new CPU architecture discovered, designed and verified by AI

https://architectlabs.com/blog/frostbite
354•shioyama•5h ago•233 comments

Show HN: I made an audio-to-MIDI model 60x more efficient

https://kobi.music/research/dettato
51•hidude562•3d ago•13 comments

Floppy3.5: A portable 3.5-inch floppy WiFi NAS

https://github.com/bigcrimping/floppy3.5
54•fortran77•1d ago•13 comments

The Making of Oxygene

https://jeanmicheljarre.com/aaa/the-making-of-oxygene
99•hggh•4h ago•36 comments

Show HN: Fast deterministic natural language search for OpenStreetMap data

https://hippomaps.ch/?q=cafes+by+the+Limmat+100+m+from+the+lake+in+zurich#map=15.02/47.36708/8.54935
67•vihren•23h ago•24 comments

Why the Airbus A321XLR often gets stuck climbing for first few hours of flight

https://simpleflying.com/airbus-a321xlr-often-stuck-climbing-1st-few-hours-flight/
54•edward•6d ago•37 comments

Signal Is Serious About Protecting Your Privacy

https://signal.org/blog/protecting-your-privacy/
86•dotcoma•5h ago•32 comments

Epic Games Turns to AI Coding for the Unreal Engine

https://spectrum.ieee.org/epic-games-unreal-engine-ai
32•rbanffy•2h ago•28 comments

What people are building, discovered through new domains

https://startups.novumsignals.com/
93•walterschnitzel•5h ago•42 comments

OpenSSL: Buffer overflow in EVP_EncodeBlock() (CVE-2026-121481, CVSS 9.8)

https://github.com/openssl/openssl/pull/33652
321•JacobHenner•13h ago•269 comments

Show HN: Tinnitus frequency finder and audio notch tool

https://trynotched.com/find
85•brianrhea•2d ago•50 comments

The G1 Garbage Collector

https://dev.java/learn/jvm/tool/garbage-collection/g1gc-overview/
7•ejboy•3d ago•2 comments

Carnival Cruises emits ten times more sulphur oxide than all of Europe's cars (2019)

https://ecohustler.com/article/one-corporation-to-pollute-them-all/
307•sammatilda•5h ago•180 comments

I can’t believe it’s 1!

https://aperiodical.com/2026/11/i-cant-believe-its-1/
29•ColinWright•3d ago•26 comments

Global stock markets slump as Anthropic's record IPO fails to stem AI sell-off

https://www.theguardian.com/business/2026/nov/20/global-stock-markets-slump-anthropic-ipo-ai-sell...
53•cdrnsf•1h ago•24 comments

FFmpeg 9.1 'Gauss'

https://ffmpeg.org/download.html#release_9.1
224•gyan•11h ago•30 comments

UK fridges secured from hackers

https://www.bbc.co.uk/news/articles/c6eq49zyx7p4o
96•tomnext•5h ago•91 comments

If you stop writing code, you also get worse at reviewing it

https://cekrem.github.io/posts/if-you-stop-writing-code-you-also-get-worse-at-reviewing-it/
71•theanonymousone•2h ago•15 comments

µ-Wire – USB on an ATtiny 10

https://cpldcpu.com/2014/03/19/%c2%b5-wire-usb-on-an-attiny-10/
82•mofosyne•2d ago•9 comments

Postgres 19 Repack: Faster, Built-In Table Bloat Cleanup

https://www.snowflake.com/en/blog/engineering/postgres-19-repack-table-bloat/
145•craigkerstiens•12h ago•24 comments

The Strongest Sokoban Solver

https://healeycodes.com/introducing-the-worlds-strongest-sokoban-solver
106•ibobev•3d ago•23 comments

How to CAD Almost Anything

https://ocw.mit.edu/courses/res-16-002-how-to-cad-almost-anything-january-iap-2024/
327•o4c•3d ago•110 comments

Jujutsu Primer

https://ethanlowman.com/posts/jj-primer/
178•renehsz•9h ago•115 comments

"I can tell you wrote this yourself"

https://em-online.bearblog.dev/i-can-tell-you-wrote-this-yourself/
308•BrunoBernardino•7h ago•296 comments

PostgreSQL 19

https://www.postgresql.org/docs/release/19.0/
302•linzhangrun•11h ago•16 comments

What Comes After AGI?

https://institute.deepmind.com/essays/what-comes-after-agi/
116•jdkee•12h ago•222 comments

Vint Cerf on why TCP/IP was never patented

https://seremot.com/p/vint-cerf-on-why-tcpip-was-never
138•emot•14h ago•68 comments

Pancreatic cancer halted by virus injection in three patients

https://www.newscientist.com/article/2528235-pancreatic-cancer-halted-by-virus-injection-in-three...
838•cybermango•21h ago•143 comments
Open in hackernews

A Taxonomy of Bugs

https://ruby0x1.github.io/machinery_blog_archive/post/a-taxonomy-of-bugs/index.html
52•lissine•1y ago

Comments

mannykannot•1y ago
Here's a step 0 for your debugging strategy: spend a few minutes thinking about what could account for the bug. Prior to its occurrence, you are thinking about what could go wrong, but now you are thinking about what did go wrong, which is a much less open-ended question.
marginalia_nu•1y ago
I've had large success by treating the bug as a binary search problem as soon as I identify an initial state that's correct and a terminal state that's incorrect. It seems like a lot of work, but that's underestimating just how fast binary searches are.

Depends of course on the nature of the bug whether it's a good strategy.

readthenotes1•1y ago
I was such a bad developer that I realized I had to automate the re-running of parts of the system to find the bugs.

Of course, the code I wrote to exercise the code I wrote had bugs, but usually I wouldn't make offsetting errors.

It didn't fix all the problems I made, but it helped. And it helped to have the humility when trying to fix code to realize I wouldn't get it the first time, so should automate replication

bheadmaster•1y ago
> I had to automate the re-running of parts of the system to find the bugs

Congratz, you've independently invented integration tests.

tough•1y ago
I don't always test but adding a lil test after finding and fixing a bug so you don't end up there again a second time is a great practice
bheadmaster•1y ago
Congratz, you've invented regression tests.
quantadev•1y ago
Congrats, you've found someone who failed to invoke a buzzword that you know.

EDIT: But Acktshally `the code I wrote to exercise the code I wrote` is a description of "Unit Testing", not integration testing.

bheadmaster•1y ago
Unit/integration tests are anything but a buzzword. And my intentions were not to belittle, but to praise.

Some actions simply make so much sense to do, that any sensible person (unaware of the concept) will start doing them given enough practice, and in process they "reinvent" a common method.

keybored•1y ago
> And my intentions were not to belittle, but to praise.

With the stock eyeroll dismissal phrase.

alilleybrinker•1y ago
There's also the Common Weakness Enumeration (CWE), a long-running taxonomy of software weaknesses (meaning types of bugs).

https://cwe.mitre.org/

Animats•1y ago
The Third-Party Bug

Is the party responsible for the bug bigger than you? If yes, it's your problem. If no, it's their problem.

marginalia_nu•1y ago
A subcategory of the design flaw I find quite a lot is the case where the code works exactly as intended, it's just not having the desired effect because of some erroneous premise.
djmips•1y ago
John Carmack uses a debugger
quantadev•1y ago
As far as you knew that guy was aware what Unit Testing was since well before you were born. lol. I'm sure he appreciates all your nice compliments.
bheadmaster•1y ago
Good thing he has knights in shining armor like you to defend him from my nasty insults.
quantadev•1y ago
Good thing you can admit what you were doing.
bheadmaster•1y ago
Good thing you can understand sarcasm.
quantadev•1y ago
but your sarcasm was truthful.
bheadmaster•1y ago
but it wasn't.
quantadev•1y ago
Well in that case...Congratz, you've invented sarcasm.
bheadmaster•1y ago
Congratz, you've invented obnoxiousness.
quantadev•1y ago
Not "independently reinvented" ?
readthenotes1•1y ago
I was aware of unit testing before it had a name ... Desperation is the mother of intervention
quantadev•1y ago
Yep, I "independently reinvent" the wheel every day I guess, because I, ya know...use wheels.