Alex Brown

Personal update: I've quietly but officially accepted an offer to join the @fireship_dev team full time! 🔥 A big switch to "behind the scenes" from what I am used to do. I love being involved in all aspects of supporting & augmenting a large scale video production pipeline.

Introducing CodeRabbit Plan. Hand those prompts to whatever coding agent you use and start building!

@jamwt @convex Let's go 🚀🚀🚀

Great chart, better stat: over 200% NRR. On average, the customer that gave us a dollar in Dec 2024 gave us two last month. That's trust and love. Want to reinvent the cloud and empower a generation to build? @convex is hiring. And we aren't just reselling tokens at a loss.

I've been a bit quiet here lately, but it's about time for an update: Fireship is officially merging with @uidotdev. @tylermcginnis and the team make great courses and I've been a fan of Bytes since it launched. We actually talked about merging together back in 2021, but the timing wasn't right. Turns out it just took a few years. For a little more context, ~18 months ago I sold a part of Fireship to a company called Electrify that invests in educational YouTube channels and helps build a team around them. I did this for 2 reasons: - Money - Time Most people don't realize that until recently, Fireship has always been a one-man show. I started with zero video production skill and zero expectations. I spent thousands of hours on a mission to make programming videos I’d actually want to watch. And somehow, I just kept making videos and it just kept working for the past 8 years… I now have 3 kids with a 4th on the way. Running and scaling everything by myself isn’t sustainable anymore, and tbh, I never had the desire to manage people. I'm a hardcore introvert who just likes making YouTube videos. So over the last year Electrify has helped me start building a team so I can focus on just the creative side. But the results have been mixed so far as we’ve tried adding to the team while still making content. Despite the rumors, I have not been replaced by AI. If I had been, uploads would be way more consistent. The reality is that making this weird style of niche technical content is hard. AI can't do it, and it turns out most humans can’t do it very well either. So we're changing things in 2026, and merging with the uidotdev team is the first step. Going forward, we’ll be making more old school Fireship programming videos, more 100 Seconds videos, and more Code Reports on a wider range of topics, along with some crazy new ideas I think you'll like. We’re also hiring more full time developers who are good at writing about technical topics. Editing and shitposting skills are also welcome. DM Tyler if you’re interested. Yes, this all takes money, which is why we have more sponsors now. That’s the tradeoff for being able to build a team. And no, I’m not stepping back. I'll still be voicing and working on every video, and I still have creative control to decide what we make. But the hope is that expanding the team will let us make more stuff and go deeper on everything without me burning out. Also, existing Fireship Pro customers now get access to all uidotdev courses and vice versa. Check out the new fireship .dev site if you’re curious. And finally, a huge thank you to everyone who has supported the channel over the years. I genuinely appreciate it more than I can put into words.

"You’ve probably heard the joke about how Model Context Protocol (MCP) is the only piece of technology that has more builders than users – to which I say, “have we all forgotten about NFTs that quickly?” bytes.dev/share?ck_subsc…

@holdenmatt @dalmaer We haven't met, but this brought back some deep memories of 4th grade. Awesome prop!

@dalmaer I don't think there was one. Katie might have some clips, but you just gotta be there in person 😉 I was awkwardly carrying this wreath around for a few hours beforehand, it's a fun prop

Fun talk last night at the AI Builders demos at Colorado Startup Week. I talked about Markdown coding, blather coding, and the 300-year evolution of punch cards from the Jacquard loom to Babbage to the 1890 Census and IBM. We're still moving up the ladder today

Chef is now open source. Also, we expanded our open source sponsorship program to support a bunch of great projects and developers. My thoughts...

The bytes.dev team did a great job a great summarizing some of our latest improvements from Firebase Studio! 🔥 📝 Read the full issue: bytes.dev/archives/419

Just learned that Svedit — the editing library for Svelte, not the Swedish version of Reddit — was featured in yesterday's bytes.dev newsletter. 🥹 Thank you, to whoever found it - and the right words. ;)

Excited to see @alchemy_run featured on bytes.dev bytes.dev/archives/417

Here is what our traffic looked like for the past 7 days after being #1 on the cool bits in the @bytesdotdev newsletter be sure to check it out and subscribe. it's frontend focused, it's silly, and it slaps

hashbrown v0.2 launch hits the #1 spot on the cool bits in @bytesdotdev as a longtime sub to this newsletter, this is an incredible shout out for what the team is building read more: hashbrown.dev/blog/2025-07-1…

@xlr8harder @eigenrobot I read @bytesdotdev newsletter religiously It’s entertaining and I learn a lot of stuff

@threepointone @bytesdotdev 🫶🫶🫶

happy 400th to @bytesdotdev, my favourite js newsletter / brand

.@bytesdotdev is awesome. Accurate and completely in tune with the latest news, but also hilariously good content. Today's newsletter from them was 🔥

Another jewel from @bytesdotdev newsletter 😂

My fellows at @uidotdev launched the final content of their React gg course: React 19, transitions etc I can recommend: it's a really playful way to learn React from first principles With many interactive widgets, visualizations, quizzes Launch week: 30% off right now!

Love this newsletter @bytesdotdev 😆