frontpage.
newsnewestaskshowjobs

Made with ♥ by @iamnishanth

Open Source @Github

fp.

Backpropagation is a leaky abstraction (2016)

https://karpathy.medium.com/yes-you-should-understand-backprop-e2f06eab496b
149•swatson741•5h ago•62 comments

Notes by djb on using Fil-C (2025)

https://cr.yp.to/2025/fil-c.html
100•transpute•5h ago•17 comments

When O3 is 2x slower than O2

https://cat-solstice.github.io/test-pqueue/
24•keyle•4d ago•2 comments

Visopsys: OS maintained by a single developer since 1997

https://visopsys.org/
351•kome•13h ago•69 comments

We reduced a container image from 800GB to 2GB

https://sealos.io/blog/reduce-container-image-size-case-study
15•untrimmed•6d ago•8 comments

How I use every Claude Code feature

https://blog.sshh.io/p/how-i-use-every-claude-code-feature
272•sshh12•11h ago•86 comments

Claude Code can debug low-level cryptography

https://words.filippo.io/claude-debugging/
330•Bogdanp•16h ago•163 comments

Updated practice for review articles and position papers in ArXiv CS category

https://blog.arxiv.org/2025/10/31/attention-authors-updated-practice-for-review-articles-and-posi...
454•dw64•20h ago•208 comments

Crossfire: High-performance lockless spsc/mpsc/mpmc channels for Rust

https://github.com/frostyplanet/crossfire-rs
69•0x1997•8h ago•6 comments

Pomelli

https://blog.google/technology/google-labs/pomelli/
186•birriel•12h ago•64 comments

LM8560, the eternal chip from the 1980 years

https://www.tycospages.com/other-themes/lm8560-the-eternal-chip-from-the-1980-years/
49•userbinator•6h ago•17 comments

FlightAware Map Design

https://andywoodruff.com/posts/2024/flightaware-maps/
26•marklit•5d ago•10 comments

GHC now runs in the browser

https://discourse.haskell.org/t/ghc-now-runs-in-your-browser/13169
312•kaycebasques•18h ago•100 comments

Show HN: Why write code if the LLM can just do the thing? (web app experiment)

https://github.com/samrolken/nokode
334•samrolken•17h ago•239 comments

Automatically Translating C to Rust

https://cacm.acm.org/research/automatically-translating-c-to-rust/
63•FromTheArchives•1w ago•15 comments

Anonymous credentials: rate-limit bots and agents without compromising privacy

https://blog.cloudflare.com/private-rate-limiting/
68•eleye•10h ago•33 comments

SQLite concurrency and why you should care about it

https://jellyfin.org/posts/SQLite-locking/
309•HunOL•22h ago•140 comments

Hyperbolic Non-Euclidean World (2007)

http://web1.kcn.jp/hp28ah77/
17•ubavic•6d ago•2 comments

Beginner-friendly, unofficial documentation for Helix text editor

https://helix-editor.vercel.app/start-here/basics/
136•Curiositry•15h ago•45 comments

3M Diskette Reference Manual (1983) [pdf]

https://retrocmp.de/fdd/diskette/3M_Diskette_Reference_Manual_May83.pdf
83•susam•5d ago•18 comments

Context engineering

https://chrisloy.dev/post/2025/08/03/context-engineering
5•chrisloy•2h ago•0 comments

Chip Hall of Fame: Intel 8088 Microprocessor

https://spectrum.ieee.org/chip-hall-of-fame-intel-8088-microprocessor
27•stmw•6d ago•1 comments

From 400 Mbps to 1.7 Gbps: A WiFi 7 Debugging Journey

https://blog.tymscar.com/posts/wifi7speedhunt/
110•tymscar•15h ago•82 comments

The Smol Training Playbook: The Secrets to Building World-Class LLMs

https://huggingface.co/spaces/HuggingFaceTB/smol-training-playbook
195•kashifr•2d ago•12 comments

CLI to manage your SQL database schemas and migrations

https://github.com/gh-PonyM/shed
24•PonyM•4h ago•11 comments

A Few Words About Async

https://yoric.github.io/post/quite-a-few-words-about-async/
52•vinhnx•10h ago•18 comments

How to Build a Solar Powered Electric Oven

https://solar.lowtechmagazine.com/2025/10/how-to-build-a-solar-powered-electric-oven/
57•surprisetalk•1w ago•28 comments

SailfishOS: A Linux-based European alternative to dominant mobile OSes

https://sailfishos.org/info/
282•ForHackernews•13h ago•116 comments

You Don't Need Anubis

https://fxgn.dev/blog/anubis/
119•flexagoon•7h ago•97 comments

Dating: A mysterious constellation of facts

https://dynomight.net/dating/
101•tobr•2d ago•95 comments
Open in hackernews

The Smol Training Playbook: The Secrets to Building World-Class LLMs

https://huggingface.co/spaces/HuggingFaceTB/smol-training-playbook
195•kashifr•2d ago

Comments

tsenturk•21h ago
Hugging Face is not just an AI information-sharing website; it’s also a great learning platform for all AI learners. This documentation is one of the most impressive hands-on resources I’ve ever read.
abossy•15h ago
What others would you recommend that are comparable in quality?
donkeyboy•14h ago
The documentation for common ai packages is pretty good too. For example, pytorch docs, peft docs, timm docs.
pixelmelt•12h ago
Been reading a book by u/fpham "The Cranky mans guide to lora and qlora" and it's pretty great, writing quality isnt all there but the content is valuable for learning to make good finetunes
lewtun•13h ago
Hi, Lewis here (one of the co-authors). Happy to answer any questions people have about the book :)
danielmarkbruce•12h ago
I'm a little ways through this and it's great so far, nice job.

One of the reasons people build one though is to learn. Most smart folks are quite aware that the reality of pre-training a real LLM is going to involve some head banging against the wall (ie, things don't go smoothly like "building an llm from scratch" book), and they want to go through the process.

forgingahead•6h ago
Where does "Smol" come from? It's supposed to mean "Small" right? If yes then what's the etymology and reason for popular usage?
potsandpans•5h ago
It's just internet speak from the days of tumbler. It usually has cutsie connotations.

Tumbler speak has a bunch of whacky things, notably "chimkin nuggers."

lewtun•5h ago
In the specific case of SmolLM, it originates from the meme in this dataset https://huggingface.co/datasets/bigcode/the-stack-smol
doctorpangloss•6h ago
I really like the Hugging Face guys, but...

> Modify one thing at a time

> Change only one variable per ablation while keeping everything else constant. If you change multiple things and performance improves, you won’t know what caused it. Test modifications individually, then combine successful ones and reassess.

This is an unintentional microcosm of what is flawed with the document.

CamperBob2•6h ago
What's wrong with it? That's good advice in almost any optimization or troubleshooting context where variables may interact.
yorwba•3h ago
One problem with testing one change at a time is that if you can only run a small number of experiments because each one requires many GPU hours to get results, you can also only test a small number of changes. If you can come up with and implement new changes much more easily than you can test them, it would be more efficient to test multiple changes at a time and use some form of Bayesian optimization to find the best combination of changes with as few experiments as possible.