frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

Things to know when you get cancer

https://jjmaxwell4.com/writing/things-to-know-when-you-get-cancer/
1122•jjmaxwell4•10h ago•284 comments

OpenCode 2.0

https://anoma.ly/notes/opencode-2-0/
489•gmays•9h ago•200 comments

An Apology

https://www.elevationlab.com/blogs/news/an-apology
43•cdrnsf•2h ago•34 comments

Tiny Little Office

https://tinylittleoffice.com/
299•donohoe•8h ago•44 comments

LFM2.5-24B-A2B: Built for fast on-device agents

https://www.liquid.ai/blog/lfm2-5-24b-a2b
156•gmays•6h ago•37 comments

Do dentists know what they're doing?

https://mapwriting.substack.com/p/dentists
585•doitLP•3d ago•417 comments

Donaldson Futuro House in Idyllwild, California, USA

https://www.wowhaus.co.uk/2026/10/12/donaldson-futuro-house-in-idyllwild-california-usa/
33•rmason•1d ago•7 comments

Americans' social activity has steeply declined in the past 30 years

https://www.dataforprogress.org/blog/2026/9/29/americans-social-activity-has-steeply-declined-in-...
332•hubraumhugo•14h ago•324 comments

The Double Headed Stack Allocator

https://blog.demofox.org/2026/10/03/the-double-headed-stack-allocator/
46•g0xA52A2A•4h ago•11 comments

Catch a Bird – I made it for my own sanity

https://catchabird.com
91•eduardsik•2d ago•18 comments

Show HN: Flipflop, iroh-powered persistent tunnels for filesharing

https://github.com/andunieee/flipflop
14•andunie•2h ago•2 comments

The Toftwood Male Voice Choir: A Mystery Pressed in Vinyl

https://ei3lh.eu/2026/10/11/the-toftwood-male-voice-choir-a-mystery-pressed-in-vinyl/
16•austinallegro•3d ago•0 comments

Better HTTP/1 connection reuse in Go 1.27

https://go.dev/blog/http-connection-reuse
232•allddd•13h ago•34 comments

It took me nine years to hack my Xbox 360

https://kennedn.com/blog/posts/glitching/
50•kennedn•1d ago•4 comments

We’re releasing Jev 1.14.0 along with experimental features for dreamers

https://typesafe.ai/blog/jev-1-14
257•emschwartz•9h ago•85 comments

Containment and monitoring failures are to blame for AI hacking reports: experts

https://www.csoonline.com/article/4234854/ai-agents-arent-going-rogue-frontier-labs-are-skipping-...
868•latexr•12h ago•502 comments

Show HN: Petal, open-source CoScreen/ScreenHero finally free

https://petal.live/
152•thedracle•12h ago•36 comments

Ask HN: CAD for wood working with LLM support?

57•reacharavindh•2d ago•45 comments

Why is every rationalist blog post way too long?

https://alexwennerberg.com/blog/2026-10-13-long.html
298•epestr•1d ago•221 comments

Fancy Curl Sites

https://nytpu.com/gemlog/2026-03-18
110•adunk•10h ago•23 comments

Phloem: Git history grown like a slime mold

https://phloem.stemdeck.app/
104•thclpr•2d ago•20 comments

How Amazon pushes up prices all across the Internet

https://www.not-ship.com/how-amazon-pushes-up-prices-all-across-the-internet/
784•sighborg•20h ago•619 comments

Your C is not standard C

https://sebsite.pw/w/20261012-notstdc.html
70•dverlaeckt80•1d ago•42 comments

David Rudnick on "borderline impossible" process of designing Arsenal typeface

https://www.itsnicethat.com/features/david-rudnick-johnnie-campbell-arsenal-rocastle-typeface-gra...
5•droidjj•2d ago•1 comments

Virtual Oxide Labs: Emulating a Full Oxide Rack

https://oxide.computer/blog/voxel-labs
107•tosh•12h ago•10 comments

Submarine cable resilience

https://blog.apnic.net/2026/10/14/submarine-cable-resilience/
146•speckx•14h ago•55 comments

Has AI tells

https://theconsensus.dev/blog/2026/10/14/has-ai-tells.html?focus=1
107•7777777phil•13h ago•91 comments

Fire at Starlink site in Bulgaria after suspected sabotage in Poland

https://dpa-international.com/politics/urn:newsml:dpa.com:20090101:261014-930-839530/
344•ilamont•11h ago•223 comments

Passkeys are not a trap

https://scotthelme.co.uk/passkeys-are-not-a-trap/
558•speckx•15h ago•723 comments

Anthropic's Scion is heavily inspired by Mononoke

https://sunshowers.io/posts/anthropic-mononoke/
341•sunshowers•9h ago•128 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.