First screen, captured . Open the video.
Full page
Captured . Click for the whole screenshot.
Looks similar
Intuiting Pratt Parsing(louis.co.nz)
141 points by signa11 | 45 comments
Nyquist Limit:The frequency of changes in tech is invalidating our understanding(ryanprior.com)
50 points by evakhoury | 21 comments
Blog post by Ryan Prior arguing that LLM-driven rapid change in software exceeds the human 'sampling rate' of understanding, using the Nyquist limit as an analogy.
Show HN: How SQL Parsers Work(nishchith.com)
11 points by inishchith | 1 comments
Parser Combinators(t3.at)
226 points by schindlabua | 81 comments
An interactive, slide-style blog post explaining parser combinators and how parsing turns unstructured text into structured data.
Related stories
The Post-AGI Era(avidfayaz.com)
10 points by Avid_F | 3 comments
A personal blog essay on Fayaz Notes arguing that AGI has arrived and exploring what the post-AGI era means.
The Twitter API is now effectively unmaintained(snarfed.org)
363 points by edent | 461 comments
Ryan Barrett's blog post arguing the Twitter API is effectively unmaintained, citing the decline of Twitter employee posts on the developer forum.
UUIDv7: Timestamps aren’t time-ordered and other oddities(alexsci.com)
150 points by ibobev | 121 comments
Blog post arguing that UUIDv7 does not reliably provide monotonic ordering, accurate creation timestamps, or unguessability, examining RFC 9562 and implementations like Python's.
What AI-Native Looks Like(fagnerbrack.com)
14 points by fagnerbrack | 7 comments
A blog post by Fagner Brack on Medium describing what an AI-native approach to software development with stable infrastructure looks like.
Claude’s memory architecture is the opposite of ChatGPT’s(shloked.com)
408 points by shloked | 216 comments
Blog post analyzing how Claude's memory system works, retrieving from raw conversation history on demand, and contrasting it with ChatGPT's memory design.
Prevent cognitive debt by manually retyping LLM-generated code(ankursethi.com)
502 points by mpweiher | 413 comments
A personal blog post arguing that developers should manually retype code generated by LLM coding assistants to keep understanding it and avoid cognitive debt.