the date is set. #Friday the 18th of December. We are running it back #BIRTHDAY STREAM and believe me you thought last years was nuts. #repost and mark your calendars people.

Channeling good vibes for the presentation at Pizza.JS

Navigating Layoffs in Real Time w/Dan DiGangi, Engineering Leader xitter.cf/i/broadcasts/1pKkOXvzv…

descobri que os argentinos criaram o MUNDIAL DE TECLADISTAS literalmente uma rinha de cumbia com chave de mata-mata, torcida e duelo de solos no teclado Mlk kkkkkkkk que conteúdo ABSURDO

Thank you so much @_christinacodes for sharing about your life, journey, hobbies - all the fun things! Seriously such an interesting person - y'all def need to follow her. And check out Resend Forward because she is working her butt off on that conf!

Hemos tenido la mejor infancia con mucha diferencia ❤️

Grandma understood the assignment. Stay ready

got laid off unexpectedly today from running postmark eng. that's life i guess. will be looking around for an eng manager spot or if anyone wants to throw a referral my way. best team i've ever had and coolest product i've worked on hands down. sad day.

12 years into my career, and for the first time I couldn't answer the question: what's next? It was winter of 2025. My feed was wall-to-wall Opus 4.5 hype (Anthropic's latest model), and my head was spinning. In a dark room rocking my one-year-old son to sleep, headphones in, I pressed play on a video Adam Wathan had just posted. He'd titled it "We had six months left." It was the moment that changed everything for me. If you remember the post, you probably felt it too. @adamwathan , the creator of Tailwindcss, opened up about the struggles Tailwind was having. Usage was up due to AI, but revenue was down, because LLMs didn't bring site traffic, which Adam's business relied on. Because of this, he had to lay off most of his staff. This was one of many stories like it. Suddenly I couldn't tell you how much of my 12 years still counted. Up until that point I didn't want to admit how big this shift was, but now there was no denying it. That night forced me to have the conversation I'd been avoiding, and ask myself: what's next for me? The way I saw it, the developer role had fundamentally changed, with parts of it being replaced by AI, some areas modified, and new responsibilities added. That realization left me with 3 paths I could take. I could keep doing what I'd always done and hope this blows over. But if the change is real, that's just failing slowly. I could get bitter and walk away, failing right away. Or I could do what developers and businesses did after the dot-com crash: accept the new landscape, figure out what actually changed and what still holds true, and play by the new rules. For developers now, this looks like new tools, new workflows, and an entirely different way of looking at the job. What it actually becomes, I don't exactly know. There's no playbook for handling decades' worth of change in a few short years. Nobody prepped us for this. We're figuring it out together. What I do know is that a new world means the death of some old ways, and the birth of ways we've never seen. And the only way out of this confusion is through.