We’re back baby

How is testing in your framework? In ember, the way you work with components in tests is no different frow your app.

If you really want to impress me, have no more than 2 redirects for SSO login

YAAAAS 🙌

Anyone know if the `prettier` maintainers are on here? Have a PR for them that I'm super eager about (since July, I think?) <excite>

FP folks are too busy rationalizing less ergonomic component apis to understand how much time they could be saving

Every distraction, in a nutshell. Including misbehaving or slow company laptops.

Even in Satisfactory, this is a bad idea. You can't efficiently merge more at-capacity belts down to fewer. Use trains.

"It's always DNS" # 87 #HomeNetworkingProblems

Every usage of untrack (or similar) is a bug. Why would you *not* want changes to signals to not get reflected in the rendered output? Don't use untrack.

> No trackpad Confirmed Neovim: vim out of the box user

Yes, and this is what ember is doing as well:

So excited for these things!!!

I don’t really get people using Storybook testing. It’s not a bad idea, and I quite like Storybook. But Storybook is constantly the most broken dependency I have, and tests are about reliability