Devon

Devon

@itsme.dev

Fullstack Engineer | Aspiring Alpaca Farmer 🦙

56 followers258 following23 posts

@tkdodo.eu Do you have any thoughts and/or examples of using @tanstack.com Query to manage SSE? Specifically, I'm adding response streaming support to an AI chatbot frontend and what was once a straightforward mutation now feels like a hacky mess.

I'm also entirely open to the suggestion that this is not a use case well suited to the library at this time.

Just migrated from Raven to the Sentry SDK. Incredible that Raven was deprecated 5 years ago, and yet the migration to the latest SDK was so simple. Really speaks to the top-notch engineering and empathy at @sentry.io!

I led the effort to drop React Native at my org. We were woefully behind on updates for all of our dependencies, and we didn't have the resources to maintain what were essentially two codebases. Instead, we've embraced the PWA, which comes with its own pros and cons 🤷

dan@danabra.mov

i bitch about it a lot but React Native is awesome. if you’re a native engineer you might feel skeptical, but it isn’t a lowest common denominator crossplatform abstraction. rather, i like to think of it as a scripting orchestration layer for platform views (which you can still write). like in games

Doing the groundwork for an eventual migration from webpack to @vite.dev. If you ever wanted to know where the bodies are buried in your codebase, try unraveling 10 years of webpack configuration and customization.

View full thread

I'm sure this must have saved the original maintainers whole seconds when writing import statements by hand, but it is now costing me my sanity 10 years later.

Doing the groundwork for an eventual migration from webpack to @vite.dev. If you ever wanted to know where the bodies are buried in your codebase, try unraveling 10 years of webpack configuration and customization.

I'm currently several weeks (part time) into removing our `resolve.modules` rule where we told webpack to look in `a/b/` for our modules... And also `a/b/c/`, and `a/b/c/d`, and `a/b/e`, and `a/b/f`, and...

The work consists of deleting the rule and then working my way through hundreds of now unresolved import errors and updating `import w from "z"` to `import w from "x/y/z"`.

I'm the sole full stack dev on a project where the other 4 devs are working exclusively on the LLM backend service. The biggest challenge is turning out to be the isolation and lack of opinions/feedback on the code I'm putting out.

You are up to date.