That would be JR Conlin, national treasure. Worked with him on YDN in 2007 and Netflix in 2009; veterans of the Netflix API team will never forget his hack day entry, which was "Mac and Me" playing on a toaster oven.
Most languages prioritize human expressiveness and can be challenging for AI. Duso is intentionally boring and predictable. No clever syntax tricks. No multiple ways to do the same thing. Every pattern is consistent and straightforward so AI can reason about code reliably, write better scripts faster, and use fewer tokens doing it.
Last night I heard Morgan Freeman solemnly intone the word "thagomizer" on Episode 2 of Netflix's The Dinoosaurs, and simultaneously felt very old but also very good.
Data sets 10 and 11 have zip archives; no archive available for data set 9. And no idea how many pages are actually in here; I'm in the 6000s and climbing with no end in sight.
... all show the same set of files, starting with EFTA00039025.pdf and ending with EFTA00039881.pdf. This is the same page you get when you ask for page 0.
Not sure how to find the end of this dataset ... setting up the server to supply an infinite number of busted Next links with something important on page 8675309 seems like a fine way to keep things hidden.
Truth: "PureGym probably has a roadmap, sprint planning, and very good reasons for not implementing Apple Wallet. Maybe it's not a priority. Maybe they have data showing only 0.3% of users would use it. Maybe their KPIs are based on the number of online classes previewed in the app, and forcing users to see them every time the app loads secures someone's annual bonus."
Oof, that one kid way out behind his seat, about to come straight down onto the front wheel? That's me, fall 1974, about to scrape most of my face right off.
That's a code smell. If you're creating the element you ought to already know about it. If you're not creating the element you should inventory them all at once as the page (or component) loads.