Minha gente, fiz um site aqui pra visualizar os casos de COVID-19 por munícipio: mapadocovid19.com.br Completamente open source, subindo nos ombros de gigantes como next.js (@zeithq), chakra-ui (do @thesegunadebayo), vx, d3.js entre outros ❤️

/teach is live Learn anything, from rubik's cube to vocal harmonies to software fundamentals. npx skills add mattpocock/skills --skill teach Best skill I've ever built, video coming soon github.com/mattpocock/skills…

Making implementation cheaper has made creating bad code cheaper But it's also made creating good code cheaper You just need to know the difference

4 of the most confusing terms in AI, defined: Model: a blob of parameters, written during training. Does next-token prediction and nothing else. Stateless. Harness: everything around the model that turns it into an agent: tools, system prompt, context window management, etc. Environment: the world the agent acts on. Anything outside the harness that the agent perceives and acts on via tools. Agent: a model, harnessed, in an environment. --- Opus is a model. Claude Code and Claude Web are different agents, because their harnesses differ - even though the models are the same. The file system is an environment. MCP servers add tools to the environment.

Writing code is cheap Maintaining code is not cheap Anyone who's hired an external contractor knows this

Just shipped Sandcastle 0.4.1. - OpenCode, Pi, Codex support - Podman, Daytona, Vercel support It's becoming the simplest way to run any agent, sandboxed anywhere

Just implemented a feature using GitHub spec-kit. It's an opinionated workflow for coding via an LLM. I used it with Claude Code, but it works with many different LLMs. Wow. It does a LOT. - Creates feature branch - Generates a high-level plan - Creates a quickstart doc for trying the feature - Generates research docs about decisions and alternatives - Outputs a detailed spec - Creates a list of tasks based on the spec - Implements tests first and enforces that they fail (TDD) - Does the implementation using task list. - Validates it all works by running linting, build, and tests (it fixed its own minor mistakes at the end too). It's VERY thorough and organized, and walks you through a highly opinionated development flow. I told it to create an admin feature for my restaurant app and it generated and implemented these 32 tasks, checking them off as it progressed. If you're coding with AI assistance, you should absolutely try this. It's a real eye-opener to how far you can take things.

Agora é oficial: sou Lead Developer Advocate na @meteorjs ☄️ “Mas pera, MeteorJS ainda existe?” Não só existe como tá mais vivo do que nunca! Tem versão nova, comunidade engajada e produtos além do framework. Ansioso pra trabalhar com open source e por tudo que vem aí ❤️

We have an announcement remix.run/blog/merging-remix…

I couldn't be happier today - we're entering a world without forwardRef ✨

React 19: Never forwardRef again

I often see aria-labels that look like an id: 🚩 aria-label="delete-user-button" An aria-label should have a *user-friendly* label that describes what the button does. And it shouldn't repeat the tag's name - that's redundant. ✅ aria-label="Delete Cory House"

We are introducing a new mode for Blocks called Lift Mode. Enable Lift Mode to "lift" components from a block template for copy and paste i.e you will be able to copy the smaller parts that make up a block template like cards, forms...etc Visit the Blocks page to try it out.

Do you love The Office? I've created a small free-to-play fan game to show some love for the series! Help me by showing this little game to the world!! enchantgames.itch.io/a-meeti…

A developer shouldn't merely do what they're told. Why? Because it's not a developer's job to merely follow orders. We're paid to see the gaps. We're paid to collaborate with others. We're paid for our professional judgement. So: We should push back. We should point out issues. We should suggest alternatives. We should consider the big picture.

This is actually a good question (quoted below), and I have a good answer for it. I was an iOS native dev from 2012-2015 (Obj-C days) and really, really loved it. Xcode was annoying but I could get around that with various tooling (RubyMotion, cocoapods, etc) that made it so I could be in Xcode less. And I shipped native binaries. I had no intention of changing. But I run a consultancy, and my clients increasingly started asking me for Android versions as well — their users were demanding it. So I started learning Android development in 2014-2015. The problem was that my team was clearly going to have to go through a transformation: 1. I’d have to double the size of the mobile team 2. Half would be iOS, half Android 3. We were still doing web at the time, so I’d have a whole other separate team doing web 4. The costs would go up tremendously — good for me, but bad for my clients In 2015 I was also preparing to merge my company with another company to become the new Infinite Red. As we were doing our due diligence, we realized both of our teams were facing this same potential issue. And with the doubled team size, it was now magnified. Because of this, my cofounder @twerth started researching alternatives in September 2015. We had heard of React Native but our assumption at the time was that it wasn’t good enough to deliver the level of user experience that we were used to. But his evaluation when he came back was “This is actually quite good.” (Remember, early days for RN! But he saw where it was going.) The primary reason it made sense was from a business standpoint. We could use the same team for all three platforms and share code, devs, training, tooling, and more. We could ship apps for about 60% of the cost (half the time with iOS plus a bit to tweak for Android). This is by far the biggest reason. But the second reason was technical. React Native is native, and the JS layer is just orchestrating UIViews and Android native views via React’s brilliant “UI as a function of state” paradigm. That meant views take up the same amount of memory as native (because they literally are native) and feel and look native to the user. With that decision made, we converted two native projects that were just kicking off to React Native and have been focused on that from then on. Now, what about personally? Truth be told, I still like iOS native dev the best. Swift is cool, and the SwiftUI declarative UI system (stolen shamelessly from React) is a good improvement over previous interface builder and xibs and programmatically / imperatively built UIs. If I was an individual dev, I’d probably lean that direction. But I’m not, and there’s almost no business case for doing native mobile dev these days when React Native exists. It’s plenty good enough in most ways and even superior in a few ways — the third party ecosystem is vast, libraries like Reanimated and Vision Camera have no equal in native land, etc. That’s why I use React Native. It is a native app in the end, just running Hermes with some bytecode to orchestrate the native UI. And I still enjoy it 8 years later!

Acusação: o podcast Xadrez Verbal é financiado por think tank dos EUA e do MBL Realidade: Padrim, dívida com os ouvintes, muita insistência minha e do Matias e só uns cinco anunciantes em nove anos de podcast Não postem sob efeitos de lisérgicos, jovens

using a <div> as a <button>

PSA: Whenever you think of writing useEffect, the only sane thing is to NOT do it. Instead, go to the react docs and re-read the page about why you don't need an effect. You really don't. But what if I ne.. - NO. read the page! In my specia.. - NO. read the page! READ THE PAGE

A common case of needless state: Dialog visibility. Example: If a dialog displays when I click on a user, I only need one piece of state, not two. And this can be streamlined even further. Here, assume UserDialog only renders when provided a user. UserDialog simply returns null if no user is provided.

components / hooks / types / utils (and constants) is the split I'm seeing in many codebases, yet it's the one I dislike the most. It groups by type, not by domain. "useTheme" will live next to "useTodo", but not next to ThemeProvider ... why?