Abdul Malik

Not making this public is heinous

@jhleath Great to hear the backstory hunter! I've seen your invaluable contributions across SDS, DOT etc. and I wish you and Archil the very best!

in summer of 2023, before my first daughter was born, and I was a product manager at EFS, I wrote a PRFAQ (codename: Minotaur) which recommended that we combine the best parts of EFS with the best parts of S3 to get to something that provided file access on top of S3. when I spoke to Andy about it, I told him that I really believe we should launch it as "S3 Files". it became clear to me that the organization wasn't actually interested in building this. my GM wouldn't take scheduled meetings about my plan, and the S3 organization was dead-set on doing what Andy speaks about publicly as "EFS3". i wasn't interesting in fighting the corporate machine (and one so good at prioritizing objects over files), so i left at the end of 2023 to join Netflix (where you won't believe what I recommended we build), and eventually to force my thinking on the world as Archil. however, almost all of my friends stayed, quietly chugging along to try to figure out how integrate EFS and S3. as Andy talks about, there were ups, downs, zigs, and zags. today, I am so very happy for my friends that not only have they successfully built a very impressive technology, but they also overcame massive organizational politics to get it launched, and (perhaps most impressively) got it the first-class branding it deserves as a feature of S3. everything is changing these days because of agents. when i defined our company in terms of a "file system on top of s3", this was privately the thing that worried me most. now that i think more in terms of how we help our developers manage context, it doesn't worry me in the same way. there is going to be plenty of time over the next few years to talk about differences, run benchmarks, and worry about marketing. today i'm happy for my friends for sticking it out to build a very very cool thing at a very very hard-to-change place.

@boristane Crazy! Ive been thinking about this too

I'm back nominal.dev

@boristane @CloudflareDev @dok2001 @ritakozlov @bjyule @irvinebroque @elithrar @baselimehq What's next?

friday was my last day at @cloudflaredev two years ago @dok2001 @ritakozlov @bjyule @irvinebroque @elithrar took a bet on @baselimehq what followed was the most rewarding chapter of my career, shipping with a team that genuinely raised my bar every day grateful doesn't cover it

I know someone who bought this for $120k 💀

Guy who created flame graphs joins Openai!

@thomasgauvin Love it!

was jealous of all the sick technical demo+blogs. So I refreshed my MCP blog post to have interactive animations, what do we think?

~8.5k lines of code

Such a cool blog! alexharri.com/blog/ascii-ren…

I worked on the Azure Blob Storage export at @posthog ❤️! I tested this with a real Azure account and worked smoothly. @posthog is a great place if you want to ship code that's used by 200k+ users. Fastest way to build real-world software skills. Try contributing!

This is a fun metric. I can imagine someone setting this as a success metric and the AI figures out it could inflate this value by repeatedly creating (and solving) bugs than actual work.

@james406 🤣

full vid on youtube youtube.com/watch?v=JAx8YA…

people tell us PostHog feels too complicated and overwhelming. we agree. in 2026, PostHog will become simpler to get started, more automated, and more powerful at the same time. i've never been more excited about what we're building

Why not just close stale PRs? @posthog has a bot that closes PRs that have no activity over 2 weeks. I recently PR'd a one-line change there and (understandably) did not get a response for a while so I tagged folks who worked on that area before. @MatlokaM was kind enough to help me out. If anyone is looking out for serious open source contributions I think @posthog is an amazing place. I recently worked on a feature for batch exports and learned a ton from the team.

This is so cool!

@posthog All contributions: github.com/PostHog/postho… Docs: posthog.com/docs/cdp/batch…

Went looking for free analytics for a side project, ended up shipping code to 200k+ customers. I discovered @posthog while hunting for a cheap way to add analytics to a side project. I was so impressed by what they offer for free that I started digging into their codebase to see if it was real. That led me to the batch exports team's sprint board, and I figured why not just pick something up and build it. 3 weeks later: 3200+ lines of code across 3 PRs, touching Temporal workflows, Django APIs, React frontend, and CI integration. The Azure Blob Storage batch export feature is now live. Before writing code, I studied how the existing export destinations were built. Just plugging in an SDK wasn't going to cut it. At this scale, I needed to understand how Azure actually handles uploads: chunking, parallel connections, retry behavior, performance tuning options. I documented these in the PR so reviewers had context upfront and future maintainers would know where to tune if needed. The implementation includes comprehensive test coverage parametrized across data models (events, persons, sessions), file formats (Parquet, JSONLines), compression types (gzip, brotli, zstd), and error handling scenarios. The team holds a high testing bar and I wanted to match it. The feature lets users export @posthog data directly to Azure Blob Storage for their data lakes and downstream analytics. Previously this wasn't an option. Thanks to @tomasfarias and @rossgray for the thorough reviews and making this a genuinely enjoyable collaboration. The founders @timgl and @james406 have built something unusual at PostHog, a billion dollar company with every line of code open sourced. The radical transparency, high ownership, and lightning fast shipping speed at this scale is genuinely rare!

@boristane Do you mean for avoiding to review it completely or do you just want its confidence on the plan

plan mode should have a llm as a judge such that I don't have to review the plans

@harkl_ @BenjaminDEKR You still need professionals maintaining and evolving these codebases. I can imagine a sort of public 'trust' that pays for agents working on these open source codebases 24/7 (of course assuming they progress to that point in the future).

@BenjaminDEKR Selling things AI can now do at basically 0 cost in a few minutes

The LLM / Tailwind CSS thing: Wait, so their entire revenue model was charging money to read the documentation? Or am I misunderstanding

It's pretty clear a new business model involving agents will soon emerge.

@boristane @theo lmao even in the thumbnail. Loved the site animations though, was that a js library for the animation? or vanilla?

damn I'm in a @theo video youtu.be/F64BLTOwQ2s?si…