Board

Yesterday Mailbrew's launch was the most successful launch we ever had: * 1200+ signups * 8500+ new brews * 5000+ site visitors Most of what we planned for it succeeded: we got good press coverag...

We have usually given a ton of importance to launch day. Again and again, at the end of the development cycle for a new product, after a week of refinements and feedback from friends and colleagues, w...

An ultimatum was what we needed to change our paths.

A living note with simple guiding principles for founders.

“Who are you and why are you here?” –Dave Cutler (DaveC)

“📣 Request for examples 📣 Mini apps and bits of software you’ve built just for yourself and/or friends and family. Things that don’t scale, aren’t meant for others to use, & valuable just for your specific, snowflake use case. Ideally custom built, but could be jerry-rigged”

Some call it as "Spaced repition"

Posts about observability written by mipsytipsy

If you’re like most of us, you learned to debug as a baby engineer by way of printf(3). By the time you were shipping code to production you had probably learned to instrument your code with …

We have developed a critical philosophy behind how we build software, and the tech stack we rely on. We call it Run Less Software.

Few companies understand their engineering strategy and vision. One consequence of this uncertainty is the industry belief that these documents are difficult to write. In some conversations it can feel like you’re talking about something mystical, but these are just mundane documents. The reality is that good engineering strategy is boring, and that it’s easier to write an effective strategy than a bad one.

A repository of computer science papers and a community of people who love reading them

Of the folks I chatted with, the most common way of learning about infrastructure engineering was working professionally with experienced peers. That is, indeed, among the most effective way to learn about infrastructure, but it’s not always an accessible option, and certainly not the only way. This is a collection of resources that I, or folks I’ve chatted to, found valuable. The majority of these resources are organized into alphabetically-ordered categories, but I wanted to start by recognizing a handful of foundational resources that I’d recommend starting with first:

h2 Why developers can’t ship code faster /h2 The current level of technology choices available to developers is both a gift and a curse. The gift is t...

Monitoring and observability are related but not the same. This blog explains the differences and why APM products can’t keep up with cloud native.

Some thoughts on how frontend developers can also embrace instrumenting their apps for observability

This is a book summary of Linchpin by Seth Godin. Check out this Linchpin summary to learn about its key ideas and lessons.

AWS bills are notoriously complicated, and the Amazon Cost Explorer doesn’t always make it easy to understand exactly where your money is going. When we embarked on our journey to reduce our AWS bill,...

In college I first heard Jason Fried from Basecamp talk about how making money is a skill—like playing the drums or piano—that you can get better at over time. That resonated with me immediately. I wouldn’t expect to be able to sit down at a piano for the first time an

Monitoring and observability are related but not the same. This blog explains the differences and why APM products can’t keep up with cloud native.

Resilient payments systems, large-scale data storage with OLTP and OLAP systems, platform team challenges, and more.