Corey Ward

If you’re using Windsurf—or another VSCode fork—and you’ve moved an extension out of the primary sidebar (the one that normally holds Explorer, Search, Source Control, etc.), you might notice there’s no obvious way to move it back.

When working with Next.js, I prefer to keep my test files right next to the code they’re testing.

Lightroom presets are an incredibly powerful tool for managing and editing your photos quickly and consistently, but as your catalog of presets grows, so too does the time you spend scrolling through those presets looking for the one you want.

I recently ran into a bug using code like the following: someArray.sort((a, b) => a.name.localeCompare(b.name)) At a glance this seems fine—localCompare enjoys fantastic browser support, and as the name suggests, it isn’t English-centric.

This is a bit of an obscure one, but I tend to use the same dev tooling configuration (Prettier, ESLint, Babel, etc) for multiple projects so I’m likely to run into this again.

I recently had the pleasure of discovering James Somer’s blog through Instapaper’s weekly “top highlights” email.

If you’re using Gatsby, you might have noticed a rather lengthy, unhelpful message in your terminal when you run yarn install or yarn add that relates to fsevents.

A recent project called for the header and footer—implemented as React components in Gatsby—to be embedded on third-party sites (think support documentation).

I recently upgraded to macOS Catalina and needed to reinstall PostgreSQL via Homebrew.

I needed to add a text-being-typed effect to a complex animation recently, and instead of cluttering up the more nuanced parts of the animation with the typing animation, I wrote a quick React Hook that takes the final string and returns the currently typ…