frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

Inkling: Our Open-Weights Model

https://thinkingmachines.ai/news/introducing-inkling/
741•vimarsh6739•8h ago•185 comments

SQLite should have (Rust-style) editions

https://mort.coffee/home/sqlite-editions/
135•gnyeki•4h ago•58 comments

Grok Build is open source

https://github.com/xai-org/grok-build
292•skp1995•6h ago•334 comments

G# – A modern .NET language with Go, Kotlin, and Swift ergonomics

https://davidobando.github.io/gsharp/
35•serial_dev•4d ago•4 comments

Governments, companies, nonprofits should invest in free, open source AI [pdf]

https://www.siegelendowment.org/wp-content/uploads/2026/07/fortune-david-siegel-open-source-ai.pdf
98•bilsbie•5h ago•44 comments

Stripe and Advent have made a joint offer to acquire PayPal – sources

https://www.reuters.com/business/finance/stripe-advent-offer-buy-paypal-more-than-53-billion-sour...
367•rvz•23h ago•215 comments

Metal-Organic Frameworks, Chemistry's New Miracle Materials (2018)

https://chemistry.berkeley.edu/news/meet-metal-organic-frameworks-chemistry%E2%80%99s-new-miracle...
42•andsoitis•3h ago•10 comments

LLM Networking with MikroTik

https://blog.greg.technology/2026/07/14/llm-networking-with-mikrotik.html
56•gregsadetsky•4h ago•19 comments

Job queues are deceptively tricky

https://typesanitizer.com/blog/job-queues.html
30•ingve•1d ago•4 comments

Running Gemma 4 26B at 5 tokens/sec on a 13-year-old Xeon with no GPU

https://www.neomindlabs.com/2026/06/08/running-gemma-4-26b-at-5-tokens-sec-on-a-13-year-old-xeon-...
242•neomindryan•11h ago•158 comments

Show HN: One More Letter

https://playonemoreletter.com/
51•hmate9•3h ago•30 comments

Duskers, the scary command line game, is getting a sequel

https://elbowgreasegames.substack.com/p/misfits-attic-announces-duskers-20
98•spacemarine1•7h ago•24 comments

Brainless: Shadcn components that look like Claude Code, Codex and Grok

https://brainless.swerdlow.dev
102•benswerd•7h ago•20 comments

Nul Characters in Strings in SQLite

https://sqlite.org/nulinstr.html
33•basilikum•3h ago•9 comments

Book prizes don't work how you think

https://rebeccamakkai.substack.com/p/book-prizes-dont-work-how-you-think
86•samclemens•1d ago•41 comments

Command Line Interface Guidelines

https://clig.dev/
77•subset•3d ago•10 comments

Prioritize mental health, and why communication is so important

https://ramones.dev/posts/mental-health/
295•ramon156•15h ago•254 comments

Mysteries of Telegram Data Centers (2022)

https://dev.moe/en/3025
242•theanonymousone•13h ago•132 comments

Voxatron

https://www.lexaloffle.com/voxatron.php
68•lsferreira42•7h ago•19 comments

Bluesky Trademarks ATProto

https://atproto.com/blog/at-protocol-trademark
7•chaosharmonic•1h ago•0 comments

CatchCat – Pokémon Go for Cats, IRL

https://www.catchcat.lol/
5•marojejian•5d ago•1 comments

Collection of Digital Clock Designs

https://clocks.dev
187•levmiseri•10h ago•36 comments

P2P local file transfer based on WebRTC

https://pairdrop.net/
37•halb•4h ago•16 comments

The Anti-Mac User Interface (1996)

https://www.nngroup.com/articles/anti-mac-interface/
57•ninglor•4h ago•20 comments

Show HN: Firefox in WebAssembly

https://developer.puter.com/labs/firefox-wasm/
143•coolelectronics•5h ago•84 comments

Artie (YC S23) Is Hiring Software Engineers

https://jobs.ashbyhq.com/artie
1•tang8330•9h ago

MITS: Rockets, Calculators, and Personal Computers

https://www.abortretry.fail/p/micro-instrumentation-and-telemetry
38•BirAdam•2d ago•3 comments

Show HN: misa77 - a codec that decodes 2x faster than LZ4 (at better ratios)

https://github.com/welcome-to-the-sunny-side/misa77
133•nonadhocproblem•10h ago•40 comments

Designing APIs for Agents

https://www.freestyle.sh/blog/opinion/designing-apis-for-agents
56•benswerd•2d ago•26 comments

Towards a harness that can do anything

https://eardatasci.github.io/c/ambiance/index.html
174•evakhoury•12h ago•89 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.