The 2nd edition of my "React Key Concepts" book is available now"! Fully updated for React 19, including brand-new chapters on RSC, form & server actions, Suspense and much more! If you, like me, like picking up a book for learning from time to time and you're (like me), convinced that we'll still need (React) devs in a couple of years, this book will be perfect for you! PLUS: There are special bonus offers & packages available now for the launch!

Who would've guessed that the Fable video game would not be the most hyped up release of the year

Somehow I'm currently in the worst possible spot. AI feels (!) good enough that hand-coding feels inefficient. But it's bad enough that it's nowhere near to doing it on its own. Hence thus far it has simply removed the fun part and ensures that I never enter the coding flow state. Instead it's that weird mixture of reviewing fixing code, writing some of it, writing specs and prompts, and trying to figure out how to become better at all these tasks.

🚀 HUGE speaker announcement! @maxedapps is coming to #CityJSAthens 2026! Bestselling author, entrepreneur, and world-renowned instructor who has taught 3M developers worldwide. This is one conference you can't afford to miss! 🎟️ athens.cityjsconf.org

Supply chain attacks, broken code everywhere, mass layoffs that are justified "because of AI", stupid / dangerous AI-powered customer support (hi meta!), AI gurus selling you their latest skills and "must use workflows" ... glorious times :)

Props to @maxedapps for trying AdonisJS over a live stream youtube.com/live/VajRzryYnvk… Loved the candid struggles 😅

No week without one...

This perfectly sums up one of the biggest issue of current-gen LLMs & coding agents

Told you so yesterday: youtu.be/nLgmTis9uM0

The 4d chess move will be to find a CVE and wait with publishing it until you got a supply chain attack ready for the patches required by the CVE

Supply chain attacks are becoming more frequent - obviously also because of AI (easier to look for vulnerabilities, write malicious code AND more targets!). But imagine the fun you'll have once you got the first compromised AI agents going rogue on your systems... Not a question of IF ... just WHEN

No month (week?) without a new huge supply chain attack. We'll see more of those. AI obviously helps with finding attack vectors, creating malicious code, and escaping security mechanisms. But maybe more importantly, attacks are just so, so much more worth it. More software than ever is being written by more people than ever not knowing anything about what they're doing (or not caring). I'm pretty sure being an OSS maintainer has never been less fun. You're getting swamped by AI slop PRs and issues AND have to try to defend against malicious attacks like the one that's currently rolling over the npm and Python ecosystem.

Going live on YT (maximilian-schwarzmueller) & Twitch (maxedapps) in a few minutes. Also almost at 80k subs. So amazing!

Think I hate on X: - "someone just did xyz" - "many such cases" - "not trying to be mean, just genuinely interested" Sorry, had to get that off my chest 😅

GitHub is facing a huge amount of problems. Uptime / reliability issues, serious bugs and now (yesterday) a critical security vulnerability that allowed remote code execution. Is it dying?

This is absolutely insane

Nowadays I get the feeling of playing Russian roulette every time I run "bun install". And yeah, I got a secure setup. Still - not super excited about getting that supply chain attack

Since a couple of people suggested using a VPS instead of Vercel (after the Vercel security incident): Don't. There are many good reasons for using a VPS. I published a new "VPS Essentials" course this week. But security is not a strong reason for switching. Cost effectiveness / low cost (and predictability) and flexibility are better reasons. It's obviously a trade off. More details in the video.

Called it in my 2026 outlook video btw => youtu.be/5WSS8Uzvy0k

Shifting from big tech to everyone else?

I thought a model couldn't get chattier than gpt 5.4 (using it in Pi). Well ... here we are with gpt 5.5...