Finding real, quotable examples is key to my blog writing workflow. Because Google and the default web search produce a lot of junk, I use Exa, HackerNews, web search, what I've already written, and internal company docs to do this, and I recently added @semble.so to this stack.

Got @standard.site working for the @posthog.com blog 😎 posthog.com/blog/sql-par...

I wrote a 70x faster SQL parser while barely looking at the code

After the success of using agents to improve query performance through autoresearch , I wanted to try something more ambitious. I rewrote PostHog's SQL parser using multiple long-running Claude Code sessions in parallel. The result was 16K lines of…

posthog.com

This is the best blue sky post, I think about it all the time

Jeff Nichols@backwardsriver.bsky.social · 4mo ago

Boastful Quaker Oats ad, Chicago 1891

The document for my latest newsletter is 5,381 words long including: - 963 word outline - 1855 word first draft - 1299 word second draft - 1056 word final post The final word count might not be a lot, but it's the result of a lot of work. Read it here → newsletter.posthog.com/p/the-engine...

Engineering has escaped the codebase. The tools, mindset, and identity shape every function. Spend time in startup circles and you’ll hear everything from design to support referred to as engineering. I wrote about how this happened and why it matters to you. newsletter.posthog.com/p/the-engine...

The engineeringification of everything

Why every role seems like an engineering role now (and what it means for you)

newsletter.posthog.com

After 1 year of building AI agents for @posthog.com, here are the top 8 things our team learned:

I recently learned the reason why Charles is so good at his role as “generic executive”: He hops on a lot of quick calls (taking @j406.bsky.social advice to heart). What does he do on those calls? He gets advice. Here are his top 5 pieces of advice for doing this well:

After weeks researching how we do pricing at @posthog.com, I published a deep dive with all the non-obvious things I learned. Here are a few of the best ones:

Being an open-source startup has many benefits, but one that doesn’t get thought of: HIRING. The fact that @posthog.com is open source has been instrumental to our hiring process from the earliest days until now.

Thanks to LLMs, user attention and understanding has become a bottleneck for building a successful product. If you want to fully leverage the velocity these tools provide, you need to solve it. We detail how in the latest edition of Product for Engineers. newsletter.posthog.com/p/the-hidden...

The hidden danger of shipping fast

What to do when product velocity breaks the speed of adoption

newsletter.posthog.com

Wrote up the lessons @posthog.com has learned about building AI-powered features that are actually valuable, from choosing what to build to implementing it correctly to improving it. Check it out: newsletter.posthog.com/p/what-weve-...

What we've learned about building AI-powered features

How to choose the right features, implement them the right way, and make them better (for real)

newsletter.posthog.com

Who's building the next GitHub? www.ianvanagas.com/notes/disrup...

Valtown is awesome, built a Bluesky mentions bot for @posthog.com super easy 😎

@ianvph/blueskyAlert

Bluesky keyword alerts Custom notifications for when you, your company, or anything you care about is mentioned on Bluesky. 1. Query Specify your queries in the queries variable. Bluesky doesn't sup...

val.town