Product Engineer for Early-Stage Startups

Last weekend I decided to dive a bit deeper into building native Linux apps with GTK4 and Adwaita.

A lot of teams still recreate their product UI in design tools so they can maintain a design reference.

I recently came across Max Barvian’s article about fixing exit animations in React.

UploadThing’s pre-built components have internal elements you can’t style through props.

You set up a monorepo with Turborepo, pnpm workspaces, and a shared UI library.

I wanted to build one of those slick admin toolbars you see on Vercel’s dashboard.

If you’ve ever seen a hydration mismatch error involving dates, or watched your “today” highlight flicker to the wrong day on page load, you’ve hit one of Next.js’s more annoying gotchas.

Despite all the advancements in LLMs, there's one area they can only attempt to emulate: tactility.

While working with Next.js App Router (v13+), I discovered a frustrating issue: ⁠notFound() doesn't return a proper ⁠404 HTTP status code when ⁠Suspense is anywhere in your rendering path.

When working with Next.js Route Handlers in App Router, you might have stumbled upon a build error which looks something like this: [Error]: Dynamic server usage: Page couldn't be rendered statically because it used `nextUrl.searchParams`.