frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

A 3D voxel game engine written in APL

https://github.com/namgyaaal/avoxelgame
20•sph•50m ago•3 comments

Google Hits 50% IPv6

https://blog.apnic.net/2026/04/28/google-hits-50-ipv6/
11•barqawiz•34m ago•0 comments

Developers don't understand CORS (2019)

https://fosterelli.co/developers-dont-understand-cors
180•toilet•7h ago•88 comments

Zigzag Decoding with AVX-512

https://zeux.io/2026/06/17/zigzag-decoding-avx512/
65•luu•3d ago•5 comments

Loupe – A iOS app that raises awareness about what native apps can see

https://github.com/mysk-research/loupe
266•Cider9986•20h ago•92 comments

Renting a sewing machine from the library

https://www.bbc.com/future/article/20260618-the-weird-and-wonderful-libraries-of-finland
218•sohkamyung•10h ago•111 comments

Epoll vs. io_uring in Linux

https://sibexi.co/posts/epoll-vs-io_uring/
149•Sibexico•9h ago•37 comments

Building reliable agentic AI systems

https://martinfowler.com/articles/reliable-llm-bayer.html
90•sarangk90•4h ago•19 comments

Public Service Announcement: Don't Say You Use AI for Writing

https://www.satisfice.com/blog/archives/488148
35•satisfice•4h ago•19 comments

Slow breathing modulates brain function and risk behavior

https://www.cell.com/neuron/fulltext/S0896-6273(26)00339-9
182•croes•10h ago•39 comments

Show HN: TownSquare, a tiny presence layer for websites

https://townsquare.cauenapier.com/
165•cauenapier•21h ago•83 comments

15-minute at-home Lyme disease tick test

https://www.bostonglobe.com/2026/06/17/business/lyme-disease-tick-test/
106•bookofjoe•2d ago•51 comments

Excessive nil pointer checks in Go

https://konradreiche.com/blog/excessive-nil-pointer-checks-in-go/
23•ingve•2d ago•17 comments

SMPTE Makes Its Standards Freely Accessible

https://www.smpte.org/blog/smpte-makes-its-standards-freely-accessible-openingstandards-library-t...
257•zdw•15h ago•77 comments

The 100k Whys of AI

https://lcamtuf.substack.com/p/the-100000-whys-of-ai
97•surprisetalk•3h ago•49 comments

DOS Game "F-15 Strike Eagle II" reversing project needs DOS test pilots

https://neuviemeporte.github.io/f15-se2/2026/06/20/needyou.html
248•LowLevelMahn•17h ago•64 comments

UHF X11: X11 Built for VisionOS and Apple Vision Pro

https://www.lispm.net/apps/uhf-x11/
202•zdw•15h ago•38 comments

Guide to the TD4 4-bit DIY CPU

https://www.philipzucker.com/td4-4bit-cpu/
31•andrewstuart•2d ago•3 comments

Unauthorized alert sent to cell phones across Brazil

https://www.cnn.com/2026/06/20/americas/brazil-hackers-unauthorized-alert-latam
128•zdw•12h ago•91 comments

Carlo Ginzburg, Who Told the History of the Obscure, Dies at 87

https://www.nytimes.com/2026/06/17/books/carlo-ginzburg-dead.html
3•benbreen•3d ago•1 comments

Your brain was never designed for this much bad news

https://www.sciencedaily.com/releases/2026/06/260614012006.htm
164•colinprince•4h ago•106 comments

When I reject AI code even if it works

https://vinibrasil.com/when-i-reject-ai-code-even-if-it-works/
170•vnbrs•7h ago•95 comments

Running MicroVMs in Proxmox VE, the Easy Way

https://taoofmac.com/space/blog/2026/06/18/1845
18•zdw•1d ago•1 comments

Whole cross-sectional human ultrasound tomography

https://www.nature.com/articles/s41551-026-01660-4
67•lnyan•2d ago•11 comments

Armstrong Effect

https://en.wikipedia.org/wiki/Armstrong_effect
25•userbinator•5h ago•2 comments

Linux eliminates the strncpy API after six years of work, 360 patches

https://www.phoronix.com/news/Linux-7.2-Drops-strncpy
196•simonpure•11h ago•168 comments

Alice is impatient

https://brooker.co.za/blog/2026/06/19/waiting.html
91•birdculture•12h ago•26 comments

Project Fetch: Phase Two

https://www.anthropic.com/research/project-fetch-phase-two
57•stopachka•8h ago•21 comments

Temporary Cloudflare accounts for AI agents

https://blog.cloudflare.com/temporary-accounts/
206•farhadhf•21h ago•109 comments

The Lost Story of Alan Turing's "Delilah" Project

https://spectrum.ieee.org/alan-turings-delilah
15•asdefghyk•3h ago•1 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.