They’ve been going native since 2019, rewriting one page at a time. Did an interview with their team in 2024, by when they migrated most of the app to native. The last few pages still remain.
I'm so incredibly tired of seeing low-effort AI-designed web pages. I basically bounce off any new product immediately when I see it (never get a chance to judge the product itself). Lots of thin lines, glowy styles, inconsistent fonts, lots of monospace.
So if you design call it loop, call it graph, call it workflow, it's kind of all the same. If you design something that gets a trigger or gets an input and does something for you and maybe there's a decision in the way, boom, there's your graph.
And I feel like it's a very human way of doing web search, right? Because we enter things in the Google and we see all the like citations, the quotations part. But like why would we limit AI to that? If AI already visit a page, why don't just pull the entire page out?
The deal was always simple: search engines had permission to crawl sites because they were going to be sending users to those sites. If they're hitting your site half a million times for every one user they send to your site, all they're giving you is higher costs.
I don’t think this is very productive (expert users of a piece of software are notoriously bad at being able to tell if an explanation will be clear to non-experts), so I needed to find a way to identify problems with the man pages that was a little more evidence-based.
: “Your guide to navigating product leadership, the one I never had. Within these pages you’ll hear a diversity of opinions from the industry’s most successful and respected product leaders, insights that will help you lead your team and deliver exceptional products.”
Gold by Rumi and Haleh Liza Gafori. Poetry, 112 pages. A vibrant selection of poems by the great Persian mystic with groundbreaking new translations by Haleh Liza Gafori, an American poet of Persian descent. Read 1–2 poems before bed each night and thank me later.
These models don't really have this distillation phase um of taking what happened, analyzing it, obsessively thinking through it, um basically doing some kind of a synthetic data generation process and distilling it back back into the weights
They do have flame graphs in Nsight Graphics for GPU workloads, although their flame graphs are currently shallow as it is GPU code only, and onerous to use as I believe it requires an interposer; on the plus side they have click-to-source.
A perfect sized companion (~100 pages) to understanding and trusting your intuition—breaking free from external validation and building courage through three core principles.
Having said all that: I confess I enjoyed "2040." The plot is tightly constructed, the dialogue crackles (certainly for a CS professor writing a first novel), the satire at least provokes chuckles, and at just 215 pages, the action moves.
So, once you use terms “fascism,” and “Nazi,” and “denazification,” suddenly people, not just start listening, they just stop analyzing. And as a propaganda tool, this is, of course, very powerful tool.
Ann Wroe’s biography of Pontius Pilate, the Roman governor of Judaea–the man who sentenced Jesus to his gruesome death–was so overwhelmingly good that I could only read a couple pages at a time.
His life and work have influenced my own tremendously—and just a few pages into Ritchie’s essential and hopeful new book, Not the End of the World: How We Can Be the First Generation to Build a Sustainable Planet, it became clear that she was carrying on his tremendous legacy.
All of which is why simple graphs of things like ‘global historical GDP’ can be a bit deceptive: there’s a lot of particularity beneath the basic statistics of production because technologies are contingent and path dependent.
One of those business books (and there are many) that you can get the main idea within the first 20 pages and can stop reading there. I skimmed through most of it.
If you want one book to teach you everything you need to know about giving great presentations, this is the book. A film director, a psychologist, and an actor share their combined experiences to help improve your content, the design, your movements, and just about every other detail of being a great speaker. It was a slow start, but by the end, I had dog-eared dozens of pages and marked up many more which I was able to directly apply to a major talk I was working on.
If you're curious how Google built it's culture and the processes thanks to their extremely data & engineering driven nature, this is a great book. What held it back was being ~100 pages too long and Bock didn't always understand where what they did only fit at a $100Bn+, mega-profitable company. Still, the insights on the studies on their 50,000+ employees is well worth the read since so few of us can get similar statistical significance to apply to our teams.
This book is a great overview of the keys to building a repeatable sales model for your SaaS business. It's a great mix of the best lessons from Jason Lemkin and his SaaStr blog and Aaron Ross's top tier consulting work. You can skip the last 50 pages which transitions to being a bad self-help book.
If you care about privacy, or want to understand what the NSA and CIA really do to monitor Americans, this book is an important read. It explains from beginning to end how Snowden became the privacy hero he is today, why he decided to leak the information, and how he did it. It's an interesting and important read, but also probably 100 pages too long.
It's an online graphing calculator that makes it very simple to whip up surprisingly complicated graphs. I found it abundantly useful for live presentations over a stream, and what's nice is that you can share the links of what you build so that students can play with them.
Everyone needs to read this book. The observations were made in a pre-internet era, and they’re 10x as relevant today. Nothing will do more to help cure your information addiction that the healthy dose of reality provided in these pages.
My wife Amanda is the real reader in our house, and last month she came home from the library with Dreams of El Dorado: A history of the American West, by H. W. Brands. I moved quickly through its 480 pages (with an occasional photo), and thought it was one of my more enjoyable recent reads.
I've run all my sites on Jekyll and GitHub Pages for a while now. I have found it easier to manage than WordPress (particularly as I know next to nothing about databases),
This catalogue was published on the occasion of the first ever exhibition of a long-dead painter at the Museum of Modern Art. It's only about thirty pages, but it is utterly brilliant.
When you serve your pages over HTTP, anyone along the transport layer can do basically anything they want to your pages. More and more often it's becoming increasingly common for somebody in the chain of custody to do something to your pages that you don't want them to do.
A korrent is a belief a person has stated in their own words: one
sentence stating the claim, backed by a quote and a source, kept at
korrents.com.
Under a name here, the quoted block is what they actually said.
The korrent beneath it is the claim those words support, in
korrents' wording — tap it to see the record, its source, and who
else holds it.
Nobody here wrote their own korrents. They are compiled from public
statements, and a person can change their mind, which is recorded too.
About the English under a post
Some people here publish in a language other than English. Where they
do, this site shows a machine translation beneath the post, in
this typeface — the site's own, not theirs.
The post itself is never changed, moved or hidden: what is set in the
serif above is exactly what the person published, and it is what to
quote them on. A translation can be wrong in ways that matter,
especially about tone.
Only the post's own words are translated. A quoted post, a linked
article and a belief on korrents.com
are left in their original language.