Mark Dalgleish

We wrote a blog post that explains the new @ReactRouter RSC architecture a bit more, and how it makes our library APIs almost as powerful as Framework Mode. remix.run/blog/react-rou…

Kids talking trash about your music suddenly get real quiet the moment you play them Cross by Justice or Discovery by Daft Punk.

@p_naix You can run .ts files directly in Node now, but it can’t handle JSX syntax. This loader minimally allows you to run it directly without needing a build step.

@markdalgleish why though?

I made a neat little Node loader for handling JSX syntax in TS/JS files - built as a part of the Remix ecosystem, but it can be used completely standalone!

Remix 3.0.0-beta.2 is available - 140 commits since beta.0 - nearly 30 bug fixes and stability improvements - tons of API polish - reduced client JS payload - improved documentation - improved template/getting started experience

WFH on a rainy day just hits different.

I know I’m biased, but this is honestly one of the coolest websites I’ve ever seen.

Remix 3 preview is here! Go try it out!

@BrooksLybrand What’d I miss??

Should we wake up @markdalgleish

Devs: With AI, the real value you provide now is taste. Also devs: Hey LLM, is my idea good?

Oxc is pretty great.

Build step? Where we're going, we don't need... build steps. github.com/remix-run/remi…

It’s April 2nd in Australia, so I’m assuming all of these odd project announcements are 100% real.

Web developers who only get paid to make boring layouts and forms looking at Pretext.

Ladies and gentlemen I present you a @markdalgleish twitter post screenshotted to reddit then posted back to twitter - attributed to the reddit page.

@Sc_Meerkat This is what I said when I had to maintain the tests by hand, but this is exactly what’s changed.

@markdalgleish The tests are never free. There is a cost associated with modifying tests when modifying code. When you test internals the likelihood of tests requiring changes is higher.

I used to be against a lot of heavy unit testing of internals. I felt they often cost more in dev time than they were worth compared to e2e. Now that AI makes these tests effectively free, and agents use them for localised feedback, this equation has shifted back a lot for me.

“Skipping tests to get a green run was the wrong approach.” Sometimes you've gotta be patient with the little guy.

@royalicing Exactly. I used to feel like a lot of these tests cost too much to maintain, but now the agent knows when to update or discard tests and can clean up as it goes.

@markdalgleish Do you keep the tests once it’s done? I guess your point is it’s fast at rewriting tests too, so they don’t have to become a burden.

@royalicing So agents know their code works at every layer, and have a good place to diagnose and fix issues in isolation. Without this the dev loop is too slow.

@markdalgleish Are you checking that these tests do what you expect? Or is it more for the agents to stay aligned? I still think testing at the significant boundaries is what I most value. Especially because they’d be finite enough you can review them.

Coding with agents is so addictive, it’s surprisingly easy to lose track of time. I feel like there’s an extra layer of productivity gains in the fact that I can get into a flow state almost instantly, and stay there much longer.