author here, couple of things in the code i think are kinda neat: - lighting is a bfs over a 5x5 window of chunks, positions packed into one dword so a neighbour step is just an add - the mesher copies the 3x3 neighbour chunks into an 18³ padded buffer so every neighbour lookup is one movzx at a fixed offset - the calling convention gets checked by tests: sentinel values in all the nonvolatile regs + a counter for misaligned calls - explosions cast 1352 rays (just the surface cells of a 16³ cube, no trig) and dedupe hits with a hash set you "clear" by bumping a generation number

repo + download: https://github.com/BaramiDev/MineAssembly

I have followed Scott for some time because of his contributions to the fsharp learning community. He's website fsharpforfunandprofit.com is one of the best programming article websites. This talk especially is very good. I think Scott is very good at breaking down complex topics to make them seem approachable.

I’m still a beginner in Japanese, and I’ve always been amazed watching more advanced learners guess the reading and meaning of words they’ve never seen before. So I got curious and tried to actually measure how often that’s possible, by breaking words into the pieces they’re built from and checking whether those pieces give the word away.

That led me down a rabbit hole of greedy algorithms and graph theory. The idea is that if you study the right building blocks first, a lot of new words become guessable without having to memorize them individually.

The result is an anki add-on that optimizes the order of your deck so that you can guess the correct meaning and pronunciation of a card on your first attempt. You can find the add-on here, GuessWithAnki.

To get the story you can watch the video or check out the full technical write up on here.

Any feedback on the process and analysis is appreciated.

There's been a big resurgence lately in automating and interacting with sites programmatically. I've been arguing for a few years that every front-end should be embeddable as a component and have its own client side interface/api. This article is designed to show one way to do that!

The “Bug Hunt” blog post pattern is the programming world’s equivalent of a detective story. It has a theme, a main plot, side plots, a protagonist (you), an antagonist (usually also you, having introduced the bug two weeks ago in the first place). It’s captivating, keeps readers in suspense, and ends with a satisfying plot twist, or a tactical cliffhanger. And the best part is…it’s even more fun to write than to read!

I host a podcast for senior engineers and recently had Carson Gross, creator of HTMX, on as a guest. We covered how REST was originally defined, how the industry ended up calling JSON over HTTP "REST", and why he thinks returning HTML from the server is closer to the original idea.

We also got into HTMX 4, when you actually do need a SPA, and how AI changes the tradeoff between simple and clever code.

Full episode: https://youtu.be/9xs0oZN2rs4

4' video on the history of REST: https://www.youtube.com/watch?v=DbNvpiJ9gTs

Roc can achieve excellent performance as a pure FP language, I think people will enjoy reading this post which looks at a pure Roc implementation of libdeflate.