There are a *lot* of software shops in the world that would far rather have one more technical dependency than they'd like to pay for one of their 20 engineers to become the company's SPOF expert on the joys of e.g. HTTP file uploads, CSV parsing bugs, PDF generation, etc.

This lunch is 500 yen ($4.80) at Sukiya, a Japanese fast food restaurant which belongs to a category with about three big competitors.

I love the aesthetics of this category and they’re under remarked upon.

I think people underestimate QSRs in terms of social utility, but Sukiya et al describe themselves as mission-oriented enterprises. I believe this is largely sincere, and goes back to the 60s and 70s, when the clientele was primarily manual laborers who had migrated to work.

Japan was not a rich nation at the time, and day laborers in particular were both unlikely to be able to cook for themselves and unlikely to have much of a food budget, and so the chains sprung up offering an honest-to-goodness cooked meal delivered in under a minute for cheap.

This heritage continued over the years, even after Japan became a much more wealthy nation, and these chains function as social support and dignity for folks in diminished circumstances.

They also are a wee bit of a cartel, and I appreciate the aesthetics of the cartel:

Back when I was first in Japan, in the mid 2000s, there was an increase in the price of beef.

And the heads of the three chains got together, and decided that the price of the basic beef bowl needed to increase, but given the economic circumstances how could they hold the line.

Bitfinex files discovery in "Yo bro, where did our $800 million go?" action and it is every bit as interesting as you'd expect it to

Here's their CFO describing their agreement (which we know from other litigation was never contractualized because, presumably because money launderers hate paper trails):

Bitfinex's CFO was shocked, shocked to learn that the money launderer they engaged to provide money laundering services while I-swear-to-God-this-is-an-actual-quote "we learned to bank like criminals" may have from time to time lied to banks.

"Institutional constraints" means, here, "We were attempting to avoid velocity checks placed by our banking partners to detect fraud and money laundering, which would have detected our fraud and money laundering."

Money at the speed of code, yadda yadda yadda, the Bitcoin economy is surprisingly blasé when several hundred million dollars is in an interstitial state for months.

In a situation never before encountered by a financial institution: the check was not, in fact, in the mail.

It’s underremarked upon that stablecoins accomplish basically all of the original design goals for Bitcoin qua a transactional mechanism (instant free value transfer anywhere), but that nobody cares about this because nobody ever cared about that part of the pitch.

“Why do people care about stablecoins then?”

A mix of “they encourage dollar-denominated liquidity in the cryptocurrency ecosystem and discourage withdrawal of the same” and “they’re good for money laundering.”

“But they make value transfer between exchanges much faster!”

This was a solved problem in traditional finance, too, mostly through the extension of credit. (It doesn’t matter how long settlement takes if there is sufficient trust to enable credit.)

The Bitcoin ecosystem is *positively allergic* to credit, so you have to call it a coin for them to accept it. And after you call it a coin they ignore everything the world has learned about credit, like risk management.

“Stablecoins aren’t credit!”

They’re pretty much exactly credit? A tether is a zero-coupon Bitfinex bond with a non-functioning call option. I

A thing which I unironically and enthusiastically believe which is unpopular among smart people of my acquaintance: financial engineering has in the recent past and present contributed substantially to human welfare. We should hope to see more of it.

Maybe more geeks need to meet someone who says “My job is teleporting value across time and space.”

Financial engineering is sort of a squishy term. I don’t primarily mean payments infrastructure or financial rails, although both of those involve substantial engineering.

I mean more “We took a thing and performed some alchemy, and now have a new thing.”

Except instead of alchemy it is generally quite a bit of math, a huge amount of contract law and due diligence, often an impressive amount of ops work, and a dusting of technology that web devs would recognize as such.

Some people really benefit from hearing advice that everyone knows, for the same reason we keep schools open despite every subject in them having been taught before.

In that spirit, here's some quick Things Many People Find Too Obvious To Have Told You Already.

Your idea is not valuable, at all. All value is in the execution. You think you are an exception; you are not. You should not insist on an NDA to talk about it; nobody serious will engage in contract review over an idea, and this will mark you as clueless.

Technologists tend to severely underestimate the difficulty and expense of creating software, especially at companies which do not have fully staffed industry leading engineering teams ("because software is so easy there, amirite guys?")

Charge more. Charge more still. Go on.

The press is a lossy and biased compression of events in the actual world, and is singularly consumed with its own rituals, status games, and incentives. The news necessarily fails to capture almost everything which happened yesterday. What it says is important usually isn't.

Companies find it incredibly hard to reliably staff positions with hard-working generalists who operate autonomously and have high risk tolerances. This is not the modal employee, including at places which are justifiably proud of the skill/diligence/etc of their employees.

A couple months ago, I got an email out of the blue from someone I had never met or heard about.

Today, that person co-hosted a webinar with me that had over 470+ registered and 130+ live

👇 Quick lesson on how to successfully pitch partnerships and co-marketing opportunities

How did he get in contact with me?

He sent a cold email, but not just any email. It was clearly personal, relevant, and conversational.

Lesson: Notice the language he used and how he tied it back to previous webinars.

Not only was it well written, but I could also easily judge if he'd be a good fit based on the article he wrote and linked to.

It's SUPER well-written and proved that he knew what he was talking about.

Lesson: Make your "ask" as easy as possible to consider.

There were three things that made the webinar a big success:

1. Tyler sent the webinar to his email list and did a lot of promotion.

2. He prepared ahead of time and put a lot of work into the deck, even incorporating some Baremetrics assets and references.

3. He had fun

Super appreciate all the work @TylerHakes put into today's "SEO for SaaS"

If you missed it, here's the recording:

For those of you asking me if I bought my wework equity—I did not. But, not because I didn’t choose to buy it. Despite joining the company very early on, I was not offered options. Here’s a thread about what happened and my feelings about it now. /1

I joined wework in 2011 as the ~17th employee when we had 4 buildings. I was 23, naive, and didn’t know what equity or options were—I certainly didn’t know how much it could impact my financial future. When I, and the first hundred or so joined the team, /2

equity options weren’t a part of the deal and I thought nothing of it. As the company grew and we brought in more funding, the executive team decided it was time to allocate equity to its employees. It was mid-2013, about 4 years after the company started. /3

We had ~120 employees and I had been there for ~2 years. I don’t know much about what went on behind the scenes to determine who would get equity and how much, or quite frankly, why they did it at all. /4

In the process, they did a couple of things: First, the way in which they chose to allocate equity, to whom, how much, etc. was… interesting. I’ll get into that more soon. Second, for the people who were given equity options, wework made the choice *not* to backdate. /5

Subtle real advantage nobody talks about: if founders can access deeper pools of capital early/quickly, they can get bigger faster without spawning lots of competitors.

If your startup is real, pitching Sand Hill is sometimes like giving away copies of your treasure map

This advice is seldom given because most of the time and for most founders, you are still better off talking about your idea as much as possible to better understand where the dead ends are in the idea maze. Can’t do that in isolation.

Asking investors what is hot is usually less useful than asking what has worked, and what didn’t work and why? That’s how you can skip ahead and avoid death.

“All I want to know is where I’m going to die so I’ll never go there.” —Munger

A few things I've learned this year from building a small, profitable internet business from zero to $100k ARR in 8 months.

Ride the wave:

People often ask what we do for marketing, and I don't really have a good answer. You don't have to push your product as hard if you're building for a vocal community of passionate people within a growing market. They'll do most of your marketing for you.

Scratch your own itch:

If you don't experience the problem you've set out to solve, you’ll have a slight disconnect between what your problem actually is, who’s experiencing it, and how to reach them. I’ll probably never do another user test in my life.

Get specific:

The web hosting space may be crowded, but the web hosting space for Notion is not. I used to think a niche would limit the total size of my business, but If we capture 1% of all Notion users, we'd be making at least $720k/month—far beyond what's enough for me.

Use side projects as marketing:

Some of our record signup days came from one of my side projects. The only mention of it was a link to it in the footer of the page. Your side projects don't have to be clearly correlated in order to still correlate.