Hi everyone! I'm happy to finally share my portfolio!🏝️ This portfolio is an island where you can explore around to get to know me, my skills, and my work. I hope you enjoy exploring around my island! Go Explore: https://t.co/BqcM6C8q9J #threejs #threejsjourney #r3

I wrote a deep dive on a GitHub repo view optimized to feel much faster — fully streamed, instant-loading, no blue bar, and still compatible with native Cmd+F. https://t.co/2xFEsgXzMw

For linting, we first run OXC in under 5 seconds, then run ESLint for the remaining files. We’re moving to OXC type-aware mode in the coming months.

We used to run code formatting and linting as a single task. With the new architecture, we split them: formatting with @biomejs and linting with @OxcProject and @geteslint. Every script and cache runs through @turborepo.

The monorepo contains packages for web apps and React Native. We have 100% test coverage across all packages. We transpile to @typescript with @swc_rs and use a mix of @jestjs_ and @vitest_dev for testing (for example, the icons package is shared across platforms).

We started with @tailwindcss 3 and later moved to 4, where we added all design tokens as CSS variables to handle theming across all sites. At first, coming from regular CSS, it felt weird —but now, doing CSS any other way feels the same.

We were early adopters of @bunjavascript and couldn’t be happier—we use it to manage all dependencies, run local servers, and build GraphQL schemas. It would be great to run it on lambdas, but we’re waiting until that’s possible on @aws without layers.

We moved to @typescript. The new monorepo uses the latest version, and type checking now runs natively with Go in seconds.

React Compiler is used on all client components, and magic comments (# allFunctionsCalledOnLoad) are added in all chunks that load before the fold (including React).

We animate only where it makes sense, and when we do, we use Motion (@mattgperry). It’s not heavier, and performance is amazing.

@fastly (with surrogate keys) is our CDN, and those surrogate keys let us invalidate all associated keys (hashed by URL, site, and environment) across every cache layer.

Deploys now take less than 3 minutes thanks to @SST_dev with Open Next. Everything runs on AWS with lambdas(ARM), moving away from the old combo of lambdas plus containers.

RSC is the main tree, and we implement client components as leaves. Sometimes branches are made up only of RSC, and sometimes they’re a mix.

I know most of you don’t like RSC, and for many sites it’s better to keep fetching with effects, but for this case it works great. It’s slow, though —so multiple cache layers (Redis and CDN) make it instantaneous.

Both the old and new architectures use SSR. The main difference, thanks to RSC, is that instead of fetching on the client side using effects during soft navigation, we now do all the fetching on the server side (@RelayFramework utils adapted to RSC).

The old monorepo stack (Babel, Javascript, React 18 with an older version of @nextjs, Styled Components) was best in class 8 years ago, but it stalled, and over time more layers were added that ultimately made the developer experience a nightmare.

TelevisaUnivision wanted to improve all metrics, so 3 years ago @ed_hidalgo and I proposed a new architecture to enhance user experience, scalability, web vitals, developer experience, and optimize costs.

We launched the new Univision site with @nextjs and the app router a month ago, and so far the results are incredible. https://t.co/wmzMxdPtQ4 Here’s a thread of all the changes we made.

📊La estadística que nadie pidió 🔥A que equipo siguen en Twitter los equipos del Futbol Mexicano #AbroHilo de datos

So it is happening, Russia is blocking traffic coming from the USA or NATO. How that breaks things? like this, a very popular module: https://t.co/RTLTeoKo3A can't be installed because it depends on hcloud-dns which is hosted on https://t.co/8TdbICuLf4.