Type Safe process.env

I recently launched a rewrite and redesign of this personal website, I figured I'd talk a bit about the changes and new features that I added along the way!

A quick tip to implementing CSS theming that's compatible with Server Side Rendered applications!

A brief overview on how we launched The Bikeshed Podcast, including a deep dive in our recording and distribution workflows!

A quick tip outlining how to provide specific TypeScript type definitions for a local module!

Some rough thoughts on building a file-system routing based web application

Slicing software: why vertical is better than horizontal.

What if you could author an entire web application in a single file?

A quick way to handle resetting internal state in components when a parent form is submitted!

A brief look at Import Maps and package.json#imports to support isomorphic JavaScript applications!

A collection of tech talks that I regularly re-watch and also recommend to everyone!

Some features and functionality that I'd like within a React Server Component compatible framework.

A (running) collection of Bluesky tips, tools, packages, and other misc things!

A quick look at a small but powerful pattern I've been leveraging as of late!

A proposal for a minimal variant of TypeScript!

Sharing a few core recommendations when working within monorepos to make your life easier!

This is a quick post noting that Next.js should now work with Deno v2!

React components have a fundamental contract that is often unstated in their implementation, and you should know about it!

Replace that old useState and useEffect combo for a new and better option!

A quick look at the applications and tools that I (generally) use day to day for web development!

There are a variety of different markdown "standards" out there, and sometimes they're not all that consistent

Proposing a solution for sharing core "business" logic across services!

There's a common gotcha when creating Web Request and Response instances with Headers!

Feature toggles are often underused by most software development teams, and yet offer so much value during not only feature development but also refactors

A quick introduction to my new side project, hohoro. An incremental JS/TS library build tool!

Two neat tricks for enhancing your site's favicon!

The various risks and pitfalls of open source software run by corporations.

A monorepo template for managing a library and documentation together.

How we solved an almost show-stopping production bug, and how you can avoid it in your own projects.

A(nother) deep dive into one of my recent side projects; tails - a plain and simple cocktail recipe app.

When did semver major changes become so scary?

Leveraging service monitors properly to improve service observability.

A brief recap of how Wayfair changed it's CSS approach not once but twice in the span of 5 years!

A deep dive into one of my recent side projects; microfibre - a minimal text posting application

Pair programming can be good sometimes - but not all the time

A few thoughts on using Suspense with GraphQL to optimize application data loading

A few thoughts on what to do after you launch a new project

A few quick thoughts on burn out and taking a break

A few thoughts on managing complex UI component state within React

A quick overview of the new lifecycle methods introduced in React 16.3

A few thoughts and patterns for using styled-jsx or other CSS-in-JS solutions

A few thoughts on the redesign of my personal site, adopting Next.js and deploying via Now

A few weird things about JavaScript

Building a calendar web application

A quick tip outlining how to provide specific TypeScript type definitions for a local module!

A quick look at a small but powerful pattern I've been leveraging as of late!

A proposal for a minimal variant of TypeScript!

A quick introduction to my new side project, hohoro. An incremental JS/TS library build tool!

Leveraging service monitors properly to improve service observability.

It's fine for a library to express some opinions about how it should be adopted and how the overall workflow/application in which it is adopted should function. However, it's false advertising to say that it is unopinionated.

No I don't mean those Milano cookies you keep taking from the office snack wall either (although you should probably stop snacking on those as often as well).

Low/no process workflow wasn't actually no process, it was only an "invisible" process. An implicit contract with everyone on the team to do that async workflow on their own time.

Replace that old useState and useEffect combo for a new and better option!