Feedly Boards

A bit more on Spotify, and then the lessons to be learned by Uber and Spotify. Plus, a potential Uber-Waymo partnership, and why they company will likely sell-out in Southeast Asia.

Take-Two buys its way into mobile, and the New York Times re-bundles.

An interview with Patreon CEO Jack Conte and Memberful CEO Drew Strojny on the occasion of Patreon acquiring Memberful, the membership software used by Stratechery. This Daily Update is free for ev…

Cloudflare dropped 8chan as a customer after this weekend’s shootings; CEO Matthew Prince explains the company’s thought process, the responsibilities of infrastructure providers, and w…

WarnerMedia’s move to stream all of its movies on HBO Max appears to be value disruptive, but if the company is actually meaningfully responding to disruption, that was inevitable.

Amazon announces Amazon One: how does it work, and is the underlying technology a good idea?

Facebook earnings demonstrated the power of its auction-based direct-response model; what makes it different from Google is Zuckerberg’s drive.

Apple and Amazon make a deal; I suspect it has been in the works for a long time, including Apple Music being on Alexa.

Spotify has acquired Megaphone, which brings clarity to its podcast advertising ambitions.

Spotify’s mixed earnings, why podcasts are uniquely valuable to the company, and where The Ringer fits in.

Epic Systems, an electronic health records company, is protesting a mandate that they make consumer health care available via API. Their arguments highlight the tension between interoperability and…

An interview with Eric Seufert about the post-ATT landscape, including Facebook, Shopify, Google, YouTube, Apple, and the future of ad agencies.

An overview of Niantic’s new developer platform, and an interview with Niantic founder John Hanke about the company’s history and future

An interview with Coda founder Shishir Mehrotra about documents, go-to-market, and competing with Microsoft, plus bundling, Spotify, and Passport.

An interview with Tony Fadell about the iPod, iPhone, Apple’s history with Samsung, Nest, the future of ARM, and his new book “Build”.

I spent a few weeks reading Ray Dalio's Principles and summarising the contents. This is the end, in which I take a final stab at contextualising the book.

Negative engineering is the time-consuming and sometimes frustrating work that engineers do to ensure small bugs don't take down systems.

Today, about 90% of public SaaS companies and the 2019 Forbes Cloud 100 have subscription-based revenue models. Now new fintech infrastructure companies have made it possible for SaaS businesses to add financial services alongside their core software product. By adding …

The market has taken a downturn, and every other blog or tweetstorm seems to offer the same general advice: conserve cash, extend runway, shift from focusing on growth to focusing on efficiency. We’ve advised many of our later stage growth …

Industry examples, exploration strategies, warm-starting, off-policy evaluation, and more.

Lifting a graph structure out of Python bytecode

A set of recommendations to make publishing a Javascript library that uses Wasm internally easier for application developers. There are a significant number of use cases and edge cases that we’ll code around as we try and cater to several types of developers: from those who may not know or care about Wasm and the broader JS ecosystem, to more experienced developers who want to optimize every last drop.

An explanation of monads in disguise

When to use generics when writing Go code, and when not to use them.

Cohesion is part of the low coupling, high cohesion principle that’s supposed to keep your code maintainable. While low coupling means few dependencies, high cohesion roughly translates to single responsibility. Highly cohesive code (a module or a function) is focused on a single purpose. Low cohesion means it does many unrelated things. I’ve written about coupling in the previous article on anti-patterns. Here are some tips on increasing cohesion in Go applications using the recently released generics.

Dockerfiles are a constant source of frustration in the container ecosystem. First, they are difficult to write (well). They can't express all types of build graphs – only linear graphs are easily expressible, limiting the amount of parallelism one can do (i.e., how fast your builds can be). Finally, they are difficult to natively integrate into build systems – passing well-known build arguments, environment variables, and other build-time variables. But what if we could easily define docker bu

The person who tells the most compelling story wins.

Faster JSON handling in a relational database.

Husky is an unbundled, distributed, schemaless, vectorized column store. Here's how we built it—and why.