frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

Escape IntelliJ: Scala and Kotlin LSPs on Emacs Eglot

https://jointhefreeworld.org/blog/articles/emacs/emacs-eglot-scala-kotlin/index.html
58•jjba23•1d ago•14 comments

Terence Tao's ChatGPT conversation about the Jacobian Conjecture counterexample

https://chatgpt.com/share/6a5fdc7a-d6f8-83e8-bbea-8deb42cfed56
872•gmays•16h ago•507 comments

Cruller: Bun's Zig Runtime, Continued on Zig 0.16

https://ziggit.dev/t/cruller-buns-zig-runtime-continued-on-zig-0-16/16734
49•Erenay09•4h ago•18 comments

git's –end-of-options Flag

https://nesbitt.io/2026/07/21/end-of-options.html
144•Erenay09•1d ago•71 comments

Quality non-fiction books are the antithesis of AI slop

https://resobscura.substack.com/p/quality-non-fiction-books-are-the
362•benbreen•19h ago•119 comments

ANSI escape injection in MCP servers: Hidden from humans, visible to AI

https://brightsec.com/research/detecting-ansi-escape-sequence-injection-in-mcp-servers-with-dast/
14•xgpyc2qp•2d ago•4 comments

GigaToken: ~1000x faster Language model tokenization

https://github.com/marcelroed/gigatoken/
503•syrusakbary•16h ago•102 comments

Show HN: Bento - An entire PowerPoint in one HTML file (edit+view+data+collab)

https://bento.page/slides/
837•starfallg•18h ago•186 comments

Everyone should know SIMD

https://mitchellh.com/writing/everyone-should-know-simd
425•WadeGrimridge•15h ago•154 comments

Amiga 1000: Ten years ahead of its time

https://dfarq.homeip.net/amiga-1000-ten-years-ahead-of-its-time/
75•giuliomagnifico•4h ago•49 comments

Are AI labs pelicanmaxxing?

https://dylancastillo.co/posts/pelicanmaxxing.html
531•dcastm•16h ago•208 comments

So Reddit has decided that plain HTML is unsafe

https://www.cole-k.com/2026/07/21/reddit/
461•montroser•21h ago•464 comments

Making ASCII Art in Vim

https://alexyang.dev/vim-ascii-art/
65•evakhoury•2d ago•6 comments

Show HN: Cactus Hybrid: We taught Gemma 4 to know when it's wrong

https://github.com/cactus-compute/cactus-hybrid
134•HenryNdubuaku•15h ago•25 comments

Making

https://beej.us/blog/data/ai-making/
358•erikschoster•18h ago•141 comments

The startup's Postgres survival guide

https://hatchet.run/blog/postgres-survival-guide
409•abelanger•21h ago•192 comments

Medici family mystery may be solved after more than 400 years

https://www.cnn.com/2026/07/15/science/medici-family-mystery-dna-malaria
123•effects•11h ago•33 comments

Protecting our FLOSS commons from LLMs

https://blog.codeberg.org/protecting-our-floss-commons-from-llms.html
53•acmnrs•8h ago•6 comments

John C. Dvorak has died

https://twitter.com/na_announce/status/2079952538040672302
750•coleca•14h ago•245 comments

Why malloc always does more than I asked for?

https://ssenthilnathan3.github.io/blog/malloc/
34•nathaah3•2d ago•25 comments

Malleable Computing, Emacs, and You

http://yummymelon.com/devnull/malleable-computing-emacs-and-you.html
110•kickingvegas•12h ago•30 comments

Fairphone 6 wide camera experimental Linux support

https://nondescriptpointer.com/articles/fairphone-6-wide-camera-linux/
121•helonaut•13h ago•32 comments

Businesses with ugly AI menu redesigns

https://blog.fiddery.com/businesses-with-ugly-ai-menu-redesigns/
292•speckx•20h ago•195 comments

ascdraw: Editor for ASCII/UTF-8 diagrams (in 144FPS)

https://github.com/exlee/ascdraw
44•xlii•2d ago•6 comments

Nobody knows what a used GPU cluster is worth

https://ciphertalk.substack.com/p/nobody-knows-what-a-used-gpu-cluster
232•rbanffy•1w ago•211 comments

Computing Camera Rays

https://momentsingraphics.de/CameraRays.html
4•ibobev•1w ago•0 comments

Restructuring GitHub's bug bounty program

https://github.blog/security/next-chapter-restructuring-githubs-bug-bounty-program/
45•soheilpro•7h ago•18 comments

Back to Kagi

https://blog.melashri.net/micro/back-to-kagi/
269•speckx•20h ago•199 comments

All 253 Patterns from Christopher Alexander's a Pattern Language Summarized

https://claytondorge.com/patterns-list
73•toomuchtodo•11h ago•13 comments

Ghost Cut – Or why Cut and Paste is broken everywhere

https://ishmael.textualize.io/blog/ghost-cut/
167•willm•18h ago•111 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.