frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

Nitter is unarchived and will continue

https://github.com/zedeus/nitter/commit/1428b4c2b4246f92a7e5b2673438e5fb39fcc4a3
230•zImPatrick•2h ago•80 comments

The car industry A/B tested selling a car with and without CarPlay

https://a.wholelottanothing.org/the-car-industry-a-b-tested-selling-the-same-car-with-and-without...
24•gumby•33m ago•10 comments

An Alien Mind

https://openai.com/index/an-alien-mind/
219•tosh•3h ago•150 comments

Your intellectual fly is open (2025)

https://bcantrill.dtrace.org/2025/12/05/your-intellectual-fly-is-open/
390•cyb0rg0•8h ago•257 comments

NetBSD 9.5 released and EOL for NetBSD-9

https://blog.netbsd.org/tnf/entry/netbsd_9_5_released_and
85•jaypatelani•4h ago•4 comments

Isar Aerospace reaches orbit and deploys payloads on second flight

https://isaraerospace.com/press/history-for-european-spaceflight-isar-aerospace-reaches-orbit-and...
491•mpweiher•13h ago•155 comments

Research carried out using NetBSD

https://www.netbsd.org/gallery/research.html
54•Bluestein•4h ago•11 comments

A/I shuts down – Stay human

https://keepitfree.ai/announcements/a/i-shuts-down-stay-human/
405•captainmuon•5h ago•268 comments

Doomscrolling Ourselves to Death

https://www.edwest.co.uk/p/doomscrolling-ourselves-to-death
299•shubhamjain•8h ago•204 comments

Babylonian Lamb Stew with Beets (1750–1730 BCE)

https://babylonian-collection.yale.edu/about/babylonian-cooking
40•yubblegum•3d ago•20 comments

Vidact – a compiler that turns React into direct DOM operations

https://www.vidact.dev/
27•mohebifar•3d ago•10 comments

Following legal advice, the Nitter project will continue

https://github.com/zedeus/nitter
245•Cider9986•2h ago•64 comments

Opalite Health (YC W26) Is Hiring – Founding GTM

https://www.ycombinator.com/companies/opalite-health/jobs/bNedVAD-founding-gtm
1•ckuo9•3h ago

Electronic skin for prosthetics to sense temperature and pressure

https://news.wsu.edu/press-release/2026/08/20/researchers-develop-electronic-skin-for-prosthetics...
25•gmays•4d ago•3 comments

Is There I/O After Death? What Happens to Io_uring When a Process Dies

https://blog.ydb.tech/is-there-i-o-after-death-what-happens-to-io-uring-when-a-process-dies-92c65...
48•porridgeraisin•3d ago•19 comments

M-DISC – DVD/Blu-ray compatible discs that may last up to 1000 years

https://en.wikipedia.org/wiki/M-DISC
160•gurjeet•4d ago•72 comments

Cloud in a Bottle: making self-hosting accessible to everyone

https://cloudinabottle.org/blog/launch-post
585•zplizzi•20h ago•289 comments

The revolt of the reader

https://bcantrill.dtrace.org/2026/09/05/the-revolt-of-the-reader/
544•chmaynard•22h ago•257 comments

Asahi Linux Now Officially Supports Apple M3 Macs – With Caveats

https://www.phoronix.com/news/Asahi-Linux-Official-M3
223•mdp2021•6h ago•139 comments

Research acceleration: The view inside OpenAI

https://openai.com/index/research-acceleration-view-inside-openai
73•iamsyr•5h ago•47 comments

Recreating Minecraft Is Not a Benchmark

https://kuber.studio/blog/Reflections/Recreating-Minecraft-is-Not-a-Benchmark
58•kuberwastaken•5h ago•45 comments

Ask HN: UK Rescue Rocket Sheds/Houses Information

12•burnt-resistor•1h ago•6 comments

Finder is so frustrating and has been since day one

https://kepter.app/finder
74•maltch•1h ago•72 comments

The many mysteries and lessons of the Bayeux tapestry

https://economist.com/interactive/culture/2026/09/03/the-many-mysteries-and-lessons-of-the-bayeux...
51•andsoitis•6h ago•9 comments

Music Theory for Programmers

https://runjs.app/blog/music-theory-for-programmers
324•birdculture•4d ago•212 comments

IBM Quantum Nighthawk R2

https://www.ibm.com/quantum/blog/nighthawk-r2
70•fuglede_•3d ago•34 comments

The pencil case model of creativity

https://dub.uu.nl/en/column/pencil-case-model-creativity
52•jruohonen•8h ago•17 comments

I'm teaching an introductory 12 week course on Quantum Oracle Engineering

https://shukla.io/quantum-oracle-engineering/
46•BinRoo•7h ago•18 comments

Ganon's Mysterious Origins (Revisited)

https://www.thrillingtalesofoldvideogames.com/blog/ganon-name-origin-kamen-rider
22•tobr•23h ago•5 comments

The ColorChecker, photography's most important 24 squares, turns 50

https://www.dpreview.com/news/the-colorchecker-photographys-most-important-24-squares-turns-50/
118•sohkamyung•4d ago•23 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.