What is Inference? How LLMs run, explained in a gentle introduction The mental model of inference: nextToken(input, frozenWeights) -> token, called in a for loop Also I explore the GGUF file that carries the ENTIRE model inside it internals-for-interns.com/posts/go-ai-... #golang #AI #LLM

Spent the weekend starting a new series: Understanding Go AI Inference. First stop: what inference actually is. A simple model is a pure function, nextToken(input, frozenWeights), called in a for loop. Every LLM answer is built one token per lap. Drops Tomorrow

Did you know? internals-for-interns.com/posts/linux-...

"The VFS" answer the question: how can file operations work identically on an ext4 file, a /proc file, and an NFS share on another machine? The answer is a classic: program against an interface, not an implementation. Read it here: internals-for-interns.com/posts/linux-...

Did you know? internals-for-interns.com/posts/mmap-v...

The first guest post in my blog, by @func25.bsky.social: "mmap vs pread in a real Go storage engine", a deep dive into how VictoriaLogs decides how to read bytes from files. It sounds too low-level to matter, until you do the math. internals-for-interns.com/posts/mmap-v... #Go

New plan for the next 3 months in my blog! Two series in parallel: Continuing the one about the Linux kernel (VFS, I/O, Devices, Network, NUMA...) And starting one about Go AI Inference (Yzma, Kronk, and friends) Plus guest posts from @func25.bsky.social, @alexrios.me @mdelapenya.bsky.social

Did you know? internals-for-interns.com/posts/go-run...

Article about the Go's Profiler CPU, heap, block, mutex, goroutine. Five profiles, one pprof file, and every sample is just a call stack. What changes is how the stack gets recorded. internals-for-interns.com/posts/go-run... #Go #Golang

Today I'm diggin into how Go profiling actually works Interesting thing, the profile file itself is just a gzipped protobuf. You can literally read the .proto and understand the whole format. github.com/google/pprof...

Did you know? internals-for-interns.com/posts/linux-...

How Linux picks who gets the CPU next, using EEVDF (Earliest Eligible Virtual Deadline First). The trick: it counts "virtual" runtime (real time ÷ priority), only lets tasks that are owed CPU run, then picks the soonest deadline. internals-for-interns.com/posts/linux-... #Linux #Kernel

Today I'm diving into how Linux decides who gets the CPU next The scheduler doesn't schedule "processes" or "threads." Underneath, both are just a task_struct. The only difference is what they share. It picks among them with an algorithm called EEVDF. Article drops Tomorrow!

This saturday I'm digging into how the go reflect package gets you the types information. Spoiler: it doesn't compute them. The compiler serialized your types into your binary. reflect just reads them with pointer arithmetic. The article will be out this Monday

Did you know? internals-for-interns.com/posts/linux-...

New article: the Linux Memory Manager On surprising fact: malloc()/mmap() reserves no physical RAM. Pages are allocated lazily, it waits until the first page fault when you touch the memory to give you the real RAM. internals-for-interns.com/posts/linux-... #Linux #Kernel #Memory

Today is my first day at @victoriametrics.bsky.social ! 🎉 Back to working on Open Source, on exactly the kind of deep systems project I've wanted for ages, performance, and understanding hardware, OS fundamentals. Lots to learn, and that's the best part. I'll be writing about what I learn as I go.

My article tomorrow about the Linux memory manager. What stuck: malloc() doesn't give you any RAM. It just reserves a range of addresses. The first time you write there, the CPU faults and *only then* does the kernel grab a real page. Alloc 1 GB, touch 10 MB, use 10 MB. #Linux #Kernel #Memory

Did you know? internals-for-interns.com/posts/go-run...

A Go panic trace is built in two phases: → the unwinder climbs the stack, recovering each call's program counter → symbolization maps each PC to a function, file, and line The chain is rebuilt on the fly from binary metadata. internals-for-interns.com/posts/go-run... #golang #go #runtime

Saturday Go runtime dive: stacktraces A panic trace is built in two parts: → the unwinder climbs your stack, grabbing each call's program counter → symbolization turns each PC into a function, file, and line Drops Monday #golang #go #runtime

I'll be giving a full-day workshop at @gopherconeu.bsky.social 2026 in Berlin! "Advanced Go Internals: Compiler and Runtime Mechanics", June 17th. We crack open Go 1.26.1's source code and modify it directly. With some fun exercises included. Come break Go with me 😄 gophercon.eu

Did you know? internals-for-interns.com/posts/linux-...

How Linux system calls actually work? `bash` can't print to the terminal. `cat` can't read a file. Userspace is sandboxed by hardware - everything goes through the kernel, and that is done through syscalls. Read more in my article here: internals-for-interns.com/posts/linux-... #Linux #Kernel

Saturday deep dive: system calls `bash` can't print to the terminal. `cat` can't read a file. Userspace is sandboxed. Everything goes through the kernel via syscalls. read, write, open, close... they look like function calls. But they're a very different beast. Article drops on Monday.

Did you know? internals-for-interns.com/posts/go-run...

New post: the Go `select` statement It's really two features: - the compiler rewrites empty, single-case, and case+default selects away - only the general case calls `runtime.selectgo` internals-for-interns.com/posts/go-run... #golang #go #runtime

Saturday Go deep dive: the `select` statement It looks like a switch, but it's really two features in one: the compiler rewrites the easy shapes away, and the runtime handles the rest in a single function called `selectgo`. I'll explait it on my Monday's blog post! #golang #go #runtime

Did you know? internals-for-interns.com/posts/linux-...

🥳We are extremely glad to announce the Schedule and the Speakers of GoLab 2026! golab.io/schedule

New article: The Linux Kernel Startup 🚀 First of a series on the Linux kernel. Not to make you an expert, just to map the territory. Heads up: it ended up denser and longer than I'd have liked, but I guess the Linux kernel is just a hard topic. 👉 internals-for-interns.com/posts/linux-... #Linux

Saturday adventure: kicking off a new series on the Linux kernel First post uses a space colony metaphor: the bootloader is the dropship, your computer is a barren planet, and the kernel is the advance team turning rock into a working colony before life support runs out. Available this Monday.

Did you know? internals-for-interns.com/posts/go-run...

New article: Slices, Maps, and Channels A look at the three most ordinary Go types and the not-so-ordinary structures behind them. ↔ slice headers and the doubling/1.25× growth ↔ Swiss tables, H1/H2, and local growth ↔ hchan, sudogs, and goroutine handoff internals-for-interns.com/posts/go-run...

Saturday Go runtime deep dive 🤓 Writing about the three things every Gopher uses every day: slices, maps, and channels. Turns out a slice is 24 bytes, a map (since 1.24) is a Swiss table, and a channel is just a buffer + two queues of parked goroutines. Will be available this Monday. #golang

The paperback of Deep Dive into a SQL Query finally arrived. I ordered a copy from Amazon to check the print quality myself, and it came out better than I expected. Different feeling seeing it on paper instead of a screen. Kindle and paperback link in the reply 👇

Did you know? internals-for-interns.com/posts/zfs-fi...

New article: Inside ZFS 🔥 A walk through the three layers (SPA, DMU, DSL), the 128-byte block pointer that makes the whole pool a Merkle tree, the uberblock ring, and why snapshots are O(1). 👉 internals-for-interns.com/posts/zfs-fi... #ZFS #Filesystems

Spent the weekend deep in ZFS internals Next up in the filesystems series: how a 128-byte block pointer turns the entire pool into a Merkle tree, and why snapshots are basically free (just copy a pointer + stamp a TXG). SPA ↔ DMU ↔ DSL, uberblocks, vdevs, ARC, ZIL. Drops Monday #ZFS #Filesystems

#gopherconEU Workshop Spotlight: Advanced #Golang Internals by @jespino.bsky.social Navigate the Go codebase from lexer and parser to the runtime scheduler. Run safe experiments on the compiler and runtime to build a concrete mental model of how Go executes gophercon.eu

As I always try after a conference, here is the summary of my experience at the Codemotion Madrid 2026. www.linkedin.com/pulse/my-exp...

Did you know? internals-for-interns.com/posts/go-net...

Saturday runtime deep dive: Go's network poller 🔍 How can you write `conn.Read(buf)` (looks blocking!) and still serve a million connections on a handful of threads? Spoiler: a smart waiter, a little note per socket, and a careful 3-step parking dance. Drops Monday #golang #runtime

Somebody from the Linux User Group at the university where I studied build this game about guessing Linux distributions. I have to admit that was harder than I expected: distro.fedesito.me

Did you know? internals-for-interns.com/posts/btrfs-...

I finally published my book about Postgres! Check it out here: lnkd.in/eakHPn6E Thanks @alexrios.me for the very good feedback, and @franckpachot.bsky.social for taking the time on reading the book and writing the foreword. More details here: www.linkedin.com/pulse/my-boo...

New article: Btrfs 🌳 The Linux filesystem that never overwrites data. Every write goes to a new location. Snapshots, RAID, per-block checksums with auto-repair on RAID, atomic transactions, all built into the filesystem. internals-for-interns.com/posts/btrfs-... #Linux #Btrfs #Filesystem

Saturday deep dive into Btrfs. The Linux filesystem that never overwrites data in place. Every single change writes to a brand new location on disk. Sounds wasteful, but this copy-on-write design is what makes instant snapshots possible. Article drops Tomorrow!

Did you know? internals-for-interns.com/posts/go-sys...

New article: The Go System Monitor How sysmon, a thread with no P, keeps the runtime fair. It preempts goroutines, retakes Ps from syscalls, forces GC every 2 minutes, and ensure network poller keeps ticking. The Go's watchdog internals-for-interns.com/posts/go-sys... #golang #go #runtime