The future was way cooler when it looked like this.

pre-pmf is going to test you like nothing before there's no blueprint, there's no right answer, everything you do is a wild swing that could hit or miss, but way more likely to miss startups are hard

your honor, i was in founder mode

wait he open sourced the whole thing goddamn

free open source chat with your pdf, running 100% on cloudflare you can literally run this for free this is wild

Looking forward to seeing the new Workers KV metrics UI (and underlying API!) ship Very Soon™

it's what you think it is 🤫 2.5 weeks to @cloudflare birthday week (!!)

Congrats to two Workers Launchpad companies, Ninetailed and Vantyr, on getting acquired last month. The next great startups are built on Cloudflare Workers. Stay tuned for the next cohort announced during #BirthdayWeek. 🎂

This is what caught my eye with Cloudflare workers in the first place. Performance is - as James Eastham says - off the charts. Anyone used them for APIs as a core part of their stack yet?

It's a little-known fact that should be MUCH better known: that AWS has been using arbitrarily-wide structured logs internally to understand core services for AGES. They don't use the term "canonical logs", so it's just about impossible to find them talking about it. But true.

I use cloudflare Spend $5/mo Profit $10000 in 6 months

what structured logs format do you use? baselime supports json super well, but I know some people do key:value pairs in other formats we refactored and these are now easy to add, drop your format and I'll add a parser

I'm using metrics send help

we're building observability 2.0 directly within the workers platform the stuff you usually only get with heavy instrumentation, and costing $$$$$ we're making it native to our cloud

guess what this test subject worker was testing?

we shipped react real user monitoring a few months ago literally for the lolz and today it gets almost 5k downloads weekly

waiting for the golang cloud fundraising announcement

one common misconception about wide events is that you should have 1 wide event per request that's not true sprinkle those events all over, just make sure each of them is context-rich, enabling you to understand unknown unknown and use the right o11y tooling for querying