The part that resonated most for me is the mismatch between agentic coding and our existing social/technical contracts (git, PRs, reviews). We’re generating more code than ever but losing visibility into how it came to be prompts, failures, local agent reviews. That missing context feels like the real bottleneck now not model quality.
Really enjoyed this perspective. Framing Bitcoin as the convergence of decades of economic and cryptographic ideas and judging altcoins by what they trade off—adds a lot of clarity. The long term historical lens feels refreshing in a space that’s usually dominated by short-term hype.
Really solid discussion on maintainability. I liked the recurring theme that clarity beats cleverness, especially the points on over-abstraction RFCs as a cultural tool and documentation focusing on why instead of restating code. The examples from consulting and legacy systems made it feel very grounded and practical.
Nice explanation of elliptic curves especially the emphasis on how the underlying field changes what the curve actually is. The transition from intuitive equations to the formal definition (smooth, projective genus one) is very well done and the Curve1174 example helps clarify why not all elliptic curves look like Weierstrass forms
This hits a really nice sweet spot. I like the focus on vanilla HTML/CSS with 11ty instead of pulling in a full React stack just for docs. The shadcn-style design system plus LLM-friendly exports are thoughtful touches and the nothing to sell positioning is refreshing. Feels like a great option for teams that want docs without framework overhead.
Appreciated. That's pretty much what I was going for.
The only thing I think is missing is a proper full text search which I'll add later on this week using lunr.js [1]. I just didn't have the time to get it done for this release.
This is a really solid deep-dive. I like how you move from this seems obviouscases (ints, strings) into the subtle edge cases where ordering quietly breaks and then show practical encodings that actually work in byte-lex order. The examples make the pitfalls very concrete, especially the varint and tuple sections. Nice balance between theory and systems-level pragmatism
In contrast, I found it rather lacking. No discussion of the most common way to sort floats as bytes (shift the sign bit down and XOR the other 31 bits with the resulting masks), nor NaNs and +/-0 for that matter. Varint sorting introduces its own homegrown serialization but doesn't discuss the issue of overlong encodings. Nothing about string collation or Unicode issues in general. Composite data suggests adding NULs, but what if there are NULs in the actual data? (It is briefly mentioned, but only as in “you can't”.)
author here -- agreed on all fronts. Mentioned this in the other comment but I approached the topic from a relatively narrow perspective (I was working on a specific project at the time)
I think it's worth including these things in a future update to the post, but I didn't have the time / need to explore it back then.
Sure, not all posts want to be the end-all of the topic. :-)
And yes, the Joel post is a good introduction, if a bit old by now. Notably, of course, it doesn't say anything about _processing_ Unicode text. (E.g., don't sort by code point, don't break in the middle of a grapheme cluster, etc. etc.) But I believe that this is outside the scope of his intention.
Big move. This feels less like a typical merger and more like a bet that AI-driven skills platforms need real scale to matter. Curious to see whether this actually improves learning quality and outcomes—or just creates a larger marketplace with the same challenges.
This was a really interesting read. I’ve always felt the “happiest country” headlines were a bit off, and this explains why. Asking one ladder question and calling it happiness feels like a stretch. Life satisfaction, mood, stress, and mental health are very different things, and mixing them together creates a pretty misleading picture. Feels like the media just loves the ranking more than the reality.
This is a huge trust failure. A VPN or ad blocker quietly harvesting full AI conversations is the opposite of what users expect, and the fact that these extensions were featured makes it even worse. This really puts the effectiveness of browser extension reviews into question.
