🧩 Code Puzzle, a little side project I made. Each level gives you a JS snippet split into pieces. Arrange them in the right order with drag and drop to solve the puzzle. ➡️ code-puzzle.sandroroth.com Built with #React and #XState

A dash of modern CSS accomplishes so many things that used to require abstractions, dependencies, and tricks (wink, wink). This one from Christian Sabourin is a great example: custom properties, clamp()-ing, calc()-ing, counters, relational pseudo selectors, etc. css-tricks.com/css-elevator...

the latest Web Dev Challenge is available to everyone! @algolia.bsky.social asked 3 teams of devs to imagine what the UX of an AI-native web app might look like. featuring @davidkpiano.bsky.social, @shaw.city, Nadirah, @aguywhocodes.com, Syscily, and Camille, with @chuckm.bsky.social

new Web Dev Challege is up early for supporters! watch Syscily, Camille, Nadirah, @aguywhocodes.com, @shaw.city, and @davidkpiano.bsky.social as they imagine what UX might look like in an AI-native app, sponsored by @algolia.bsky.social with @chuckm.bsky.social as our advisor codetv.link/wdc/s2e6

helping the Keyframers reunion happen over here @davidkpiano.bsky.social @shaw.city

⚛️ XState Store now has atoms, and they're *really* simple. → atom.get() → atom.set(…) → Derived atoms (reactive) → Async atoms → Stores are atoms too! npm i @xstate/store stately.ai/docs/xstate-...

I like state machines. I still struggle a bit to get my mind bent into state machine shape, but I’m always so happy with the quality of what I build when I do

That's it, I'm switching to xstate store

How would you simplify XState? Planning for the next major version, and would love to hear your thoughts and ideas ✍️

Join us on today's episode as we interview David Khourshid @davidkpiano.bsky.social. We will learn about state machines and how XState plays nice with #Angular right out of the box! #ngconf 🍎https://apple.co/4ipNHcP 🟢 spoti.fi/3VxlGGq

I now *really* enjoy reading articles that are so obviously human-written, mistakes and all

I don't like default exports. They exist in JS because they're "simpler", even though they're more verbose: export default Thing import Thing from './thing' vs. export { Thing } import { Thing } from './thing' Just use consistent naming & don't be afraid of typing curly braces.

Updated demo of Decode generating state-machines from diagrams, this time with streaming generation support Then I do the reverse, generating a diagram from an implementation. The diagram auto-layout is still rough. I'll work work on more robust auto-layout soon.

🔲 Merge Conflict: Accept All Current 🔲 Merge Conflict: Accept All Incoming ☑️ Merge Conflict: Accept the things I cannot change, the courage to change the things I can, and the wisdom to know the difference

I wrote an essay about relationships that may be helpful for personal career development (and maybe devrel). Mentioned in the post (by name): @davidkpiano.bsky.social, @kentcdodds.com, @joshuakgoldberg.com, @jennytru.bsky.social, @acemarke.dev, and others tej.as/blog/how-to-...

Component State Management in React: - useState - useMachine That's it. That's all I use anymore.

FSMs are the best way to model UI state. What can we do to indoctrinate people to this fact?

Hello again, world This place seems cool

Software estimation is hard

I love TODO comments. They're like little reminders of the ambitious developer you thought you'd eventually become.

I'm not actually a piano