frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

Critical CVE issued for hallucinated SQLite vulnerability

https://research.jfrog.com/post/sqlite-critical-cves-or-llm-slops/
439•ymir_e•3h ago•143 comments

Devtools must be open source

https://blog.exe.dev/devtools-must-be-open-source
52•bryanmikaelian•1h ago•11 comments

MiniMax H3 Day-0 Support in ComfyUI: Open Weights, Native Audio, and 2K Video

https://blog.comfy.org/p/minimax-h3-day-0-support-in-comfyui
89•vblanco•1h ago•38 comments

Don't be a meat proxy

https://gruhn.me/blog/2026-08-03/
1239•ngruhn•8h ago•520 comments

Qwen3.8-Max: A New Bar for Coding and Cowork

https://qwen.ai/blog?id=qwen3.8
859•ai2027•13h ago•437 comments

Hollywood Stopped Making Movies in Hollywood

https://www.statsignificant.com/p/how-hollywood-stopped-making-movies
20•speckx•6d ago•9 comments

AirLLM 70B inference with single 4GB GPU

https://github.com/lyogavin/airllm
73•Anon84•4h ago•33 comments

SPF Record Syntax: Mechanisms, Qualifiers, Modifiers, and Macros

https://dmarcguard.io/blog/spf-record-syntax/
18•meysamazad•1h ago•3 comments

The Abandoned Fish Sauce Terrorizing a Small Canadian Town

https://defector.com/abandoned-fish-sauce-canada-interview
108•ohjeez•2d ago•70 comments

Bonsai: Janestreet's UI Library

https://github.com/janestreet/bonsai
176•KolmogorovComp•6h ago•63 comments

Prevent cognitive debt by manually retyping LLM-generated code

https://ankursethi.com/blog/prevent-cognitive-debt-by-manually-retyping-llm-generated-code/
237•mpweiher•5h ago•181 comments

Games at the press of a button: The Rip-O-Bot (1989)

https://blog.gingerbeardman.com/2026/08/02/games-at-the-press-of-a-button-the-rip-o-bot/
15•msephton•19h ago•2 comments

Andy Pavlo Joins ClickHouse to Establish ClickHouse Labs

https://clickhouse.com/blog/andy-pavlo-joins-clickhouse
16•nikolay_sivko•1h ago•0 comments

Flock's CEO Faced Me After Its Cameras Led to My Wrongful Stop

https://www.thedrive.com/podcast/flocks-ceo-wants-zero-wrongful-stops-i-wasnt-the-first
26•f154hfds•22m ago•3 comments

Rust project goals: Immobile types and guaranteed destructors

https://github.com/rust-lang/rust-project-goals/blob/main/src/2026/move-trait.md
161•paavohtl•8h ago•58 comments

Show HN: Nightcrawler – A local AI pentesting agent running on a smartphone

https://github.com/garagehq/nightcrawler/
60•NickySlicks•4h ago•20 comments

Walk on Decomposed Subdomains

https://clementjambon.github.io/wods/index.html#blogpost
17•E-Reverance•6d ago•1 comments

Train Simulator Controller

https://z80.me/blog/tsc-2026-july/
60•austinallegro•3d ago•3 comments

Octane – React's programming model, compiled

https://octanejs.dev
84•nnx•7h ago•31 comments

What DMARC Protects You From, and What It Does Not

https://senderledger.com/articles/what-dmarc-actually-protects-you-from
70•adulion•5h ago•20 comments

Show HN: Isopolis – Isometric pixel map of SF

https://sf.isopolis.city/
290•nuwandavek•14h ago•65 comments

The Future, Made in China

https://www.newyorker.com/magazine/2026/08/10/the-future-made-in-china
26•littlexsparkee•1h ago•19 comments

Finding zombies in our systems: A real-world story of CPU bottlenecks

https://medium.com/pinterest-engineering/finding-zombies-in-our-systems-a-real-world-story-of-cpu...
7•fagnerbrack•1d ago•0 comments

Show HN: We Fixed UniFi's Slow PPPoE Performance with PPPoE Half-Bridge

https://arcbox.dev/blog/unifi-pppoe-half-bridge-acceleration
51•uneven9434•6h ago•22 comments

The true power of regular expressions (2012)

https://www.npopov.com/2012/06/15/The-true-power-of-regular-expressions.html
54•uneven9434•6h ago•43 comments

Characterizing Warp Divergence from Pascal to Blackwell

https://arxiv.org/abs/2607.23402
17•matt_d•3d ago•1 comments

Why we write our own C and C++ inference engines

https://localai.io/blog/why-we-write-our-own-engines/
97•eatonphil•2d ago•39 comments

Show HN: ssh ssh.place

https://ssh.place
161•jeninh•14h ago•88 comments

Utah produced more power from solar than any other source in May, a new first

https://www.sltrib.com/news/environment/2026/08/03/utah-sets-solar-power-record/
10•toomuchtodo•1h ago•4 comments

CP/M-386 – CP/M for 386 protected mode, derived from CP/M‑68K

https://github.com/johnsonjh/cpm386
90•TMWNN•14h ago•44 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.