Edd Mann
6.8K posts

Edd Mann
@edd_mann
developer, building things - 🎙️ https://t.co/1G7Rk4OeyX








really excited to finally get this episode published 🎉 Ep. 17: Event Sourcing with Shawn McCool @ShawnMcCool shares how event sourcing fundamentally changed the way he thinks about modeling software systems. if you've ever felt stuck in the "way we've always done it" mindset, this one's for you 👇 🎧 compiledconversations.com/17/ we trace shawn's journey from discovering domain events while working on laravel.io back in 2012, through creating Event Sourcery, to now building payment processing systems. what started as curiosity about DDD turned into a completely different approach to building software. the core insight: events aren't just for messaging or streaming - they become the actual source of your model state. we dig into how this differs from event-driven architectures and why capturing intent matters more than capturing data changes. shawn shares a practical pattern that eliminates entire classes of versioning and data retention headaches: design your aggregates to exhaust quickly. at his current company, event streams naturally terminate within 30 minutes. no long-lived aggregates means no painful migrations, no GDPR nightmares. we also explore the relationship between event sourcing and CQRS, testing strategies, and why DDD isn't really a methodology - it's a pursuit of understanding your domain. full episode: 🎧 compiledconversations.com/17/

The lobster has molted into its final form 🦞 Clawd → Moltbot → OpenClaw 100k+ GitHub stars. 2M visitors in a week. And finally, a name that'll stick. Your assistant. Your machine. Your rules. openclaw.ai/blog/introduci…



really excited to finally get this episode published 🎉 Ep. 17: Event Sourcing with Shawn McCool @ShawnMcCool shares how event sourcing fundamentally changed the way he thinks about modeling software systems. if you've ever felt stuck in the "way we've always done it" mindset, this one's for you 👇 🎧 compiledconversations.com/17/ we trace shawn's journey from discovering domain events while working on laravel.io back in 2012, through creating Event Sourcery, to now building payment processing systems. what started as curiosity about DDD turned into a completely different approach to building software. the core insight: events aren't just for messaging or streaming - they become the actual source of your model state. we dig into how this differs from event-driven architectures and why capturing intent matters more than capturing data changes. shawn shares a practical pattern that eliminates entire classes of versioning and data retention headaches: design your aggregates to exhaust quickly. at his current company, event streams naturally terminate within 30 minutes. no long-lived aggregates means no painful migrations, no GDPR nightmares. we also explore the relationship between event sourcing and CQRS, testing strategies, and why DDD isn't really a methodology - it's a pursuit of understanding your domain. full episode: 🎧 compiledconversations.com/17/


Remotion now has Agent Skills - make videos just with Claude Code! $ npx skills add remotion-dev/skills This animation was created just by prompting 👇










