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.
And that kind of compiling of information about the materials is something other fields do that we don't do. An analogy that I would think of in software would be something like a 500-page book on how to version an API.
Some people think CI means you reject grammar books. I disagree. I often reference grammar materials and find these explanations useful. However, the focus of my learning is not to “master the rules”. Grammar resources simply help me notice and make sense of patterns in the language.
the ballerina and the kind of performer, that's the wrong reference class. Right now we have a lot of jobs where you have different tasks. So this is the task-based model jobs where you have like a lot of different tasks. So like a doctor, what is their job? They're filling out insurance documents. They're you know, going and like calling different pharmaceutical companies. And one of their tasks is to actually see the patient and talk to them, but that's like actually not the main part part of the job.
LLMs themselves are the perfect captive reader: they never get bored or confused, never miss a reference or have an emotional reaction, never ask themselves why am I reading this?, never close the tab.
And what this is is that in the guide level explanation, you explain your feature as if you were writing a guide as if the feature already existed. And in the reference level explanation, you explain your feature again as if it already existed, but as if it would be in the language reference instead of a tutorial.
AI today it's just starting to to become aware of you know the existence of of of language services and agents today like to use grep and awk and whatever you know to to find all the places where you reference a certain thing but it's not semantic search, right?
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.
A perfect sized companion (~100 pages) to understanding and trusting your intuition—breaking free from external validation and building courage through three core principles.
The big flaw is that it's justified through a fictional world. It's not justified through reference to the real world. It's not empirical in a way. It's not... Rand herself would say this. She's not writing about things how they are, but how they should be. That idealism just really undermines it as a mechanism to understand where we're actually living.
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 very important to keep in mind that Rus is not Russia because that was a self-name for all multiple groups on that territory. And Moscow doesn’t exist at the time when Kyiv emerges as the capital. The first reference to Moscow comes from the 12th century when it was founded by one of the Kievan princes.
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.
The Linux Programming Interface by Michael Kerrisk – an exhaustive reference on how Linux works. There are about a million chapters, but every individual chapter is pretty short and I find it quite readable.
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.
I use Roam as my main note-taking app. While I only use very basic features such as bidirectional links and reference blocks, it works well enough for me.
I was disappointed. I love Tim’s work, but this didn’t deliver in the way his past books have. There’s zero thematic organization, so you can’t reference certain topics you want to learn more about except in a few cases. While this has some interesting pieces, I doubt I’ll refer back to it like I have with Workweek, Body, and Chef.
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.
not only did I buy the canonical reference (The Rust Programming Language by Steve Klabnik, Carol Nichols and community contributors), I also bought an O'Reilly book with a bit more narrative (Programming Rust by Jim Blandy and Jason Orendorff).
I take my hat off to Hugh. This is one wine reference book that I have nothing to do with, and it is absolutely brilliant. It's very small—although, of course, it's been getting bigger and bigger as the wine world has expanded—and it does pack a heck of a lot of information.
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.
Other frequently used programs include Dreamweaver and Fetch for my site; Chrome, iPhoto and Preview for reference hunting; iTunes, Spotify, and Downcast to keep me company.
The evidence they cite in favor of cash points to peer reviewed randomized trials. The evidence on better performing programs point to… NGO home pages.
Rounding out the Bare Bones-related triumvirate is Yojimbo, a sort of junk-drawer program that lets me drop in notes, serial numbers, Web pages, images, and PDFs, and optionally encrypt individual items.
If you don’t know the book, Content Rules is the how-to field guide to creating the kind of blogs, videos, FAQs, product pages (or any kind of content!) that will help your organization grow.
Editing for the books usually happens in either Word or Pages; I have no love for either, but Word plays nicely with InDesign, so we're a little but stuck with it for now.
The book is colorful and ludic which is a good idea for a "Beginner's Guide". The layout is attractive, there are many detailed examples. I like the pedagogy: the author wants you to learn by doing. However, the book is poor as a reference: the coverage is limited despite the 300 pages and the chapter summaries are strictly non-technical.
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.