imwm

Disassemble*

The book Monetizing Innovation, to me, has been the smartest approach to pricing I've encountered: https://www.amazon.com/Monetizing-Innovation-Companies-Desig...

Basic idea is that you should design the product around the price. Do price discovery before you do anything else.

Podcast ep here: https://www.youtube.com/watch?v=A6veeCbKIzw

"The author of this article" is Jony Ive, who very possibly has dipped into other chapters of computer history

evidenced by the huge variation in word count among his short stories. some are a couple pages, while others are essentially novellas.

As Ben Thompson pointed out recently, unlike Google and OpenAI, Meta benefits from open source AI taking off because that makes everyone better content creators, which accrues further value to their social media platforms.

abcdefghijkloabcdefghijklopabcdefghijkloabcdefghijklopabcdefghijkloabcdefghijklopabcdefghijkloabcdefghijkloa

Google has the same answer tbf

Expired in 2017 which led to the recent rise of one-click checkout startups

I didn't even know he was sick

meta.com – used to be a Chan-Zuckerberg initiative to discover scientific papers. Now it's Facebook's corporate home. Hmm.

"I still like writing things out in longhand, finding that a computer gives even my roughest drafts too smooth a gloss and lends half-baked thoughts the mask of tidiness"

-Obama

I wonder if there's any metaphorical value in this phenomenon

"mars can't wait" lol

Didn't know this story was originally published in Nature. I read it in his excellent short story book Exhalation and loved it like I did many others in that collection.

Chiang is like Kafka and Borges in that he writes plain prose that blows your mind.

This would explain why NYC flattened and then reduced the first curve relatively quickly.

"Assuming the conclusion" has a clear meaning distinct from "non-sequitur."

"Non-sequitur" evaluates a statement's relationship to a previous statement.

"Assuming the conclusion" evaluates a statement on its own.

Fitting this article was written by a fella named Moore

Not a problem I've encountered, but one that will be solved by the robust extension ecosystem of VSCode. You can apply this to any UX problem you might encounter with VSCode.

I can't believe how funny this writer is

lit

"makes making"

"It didn't help that he crashed while doing so."

...is the subtitle. Might have been nice to say in the headline, which is clickbait.

We switched from Travis CI to Circle CI because Circle CI was (a) significantly faster and (b) a little cheaper