Who Is Wez Furlong and What Is His Background?

Wez Furlong is a software engineer and entrepreneur who describes himself as experienced in both roles, with much of his work over the years released as Open Source. According to his own site, his software has been widely used: he writes that "if you've ever browsed the web or received an email there's a strong chance that my software was involved." His personal site, wezfurlong.org, is where he collects his blog posts, project notes, and background information.

What the site says about him

The site's own summary is brief but specific:

• Profession: experienced software engineer and entrepreneur.
• Work style: a large portion of what he has built over the years is Open Source.
• Reach: his software has been involved in web browsing and email infrastructure, based on his own description.
• Contact: he lists a Mastodon handle, @[email protected], and notes that he offers mentoring services.

The site also links to a separate "about" page for more detail, so the homepage summary is intentionally short.

Evidence of his technical range

The site's archive and category listings show the topics he has written about over roughly two decades, from 2003 through 2024. Categories include API, MySQL, PDO, PHP, JavaScript, jQuery, nodejs, REST, Windows, Solaris, Obj-C, and conferences such as OSCON and ZendCon. That spread is consistent with a engineer who has worked across web backends, databases, and systems-level tooling rather than a single stack.

Watchman and file-system tooling

A June 2013 post describes Watchman, announced on the Facebook Engineering blog. In his words, Watchman watches files and records information about them as they change; it can trigger build or test steps when matching files change, but the main reason it was built was to answer file-status queries instantly for a set of files. It keeps a view of the filesystem in sync using kernel filesystem notification facilities and indexes that view for fast queries. This is a concrete example of the kind of infrastructure work his site documents.

The site itself

A February 2024 post explains that the site had gone a long time without updates. He migrated it from Jekyll to Material for MkDocs, partly to stop dependabot warnings about Ruby ecosystem security issues, updated his bio and photo, and added a dark mode. The post is also candid about cadence: he is not sure he will blog more regularly than "once a decade," and invites topic requests via Mastodon.

What this means if you are trying to place him

If your question is whether wezfurlong.org is a personal blog or a product site, the evidence points to a personal blog: first-person posts, an archive by year, category tags, and a short self-description. If you want to know his background, the site gives you the headline claims (engineer, entrepreneur, Open Source, widely used software) and lets the archive demonstrate the range. For specifics beyond that, the site points to its own about page and to his Mastodon account rather than offering a detailed resume on the homepage.

One caution: the homepage summary is self-reported, and the site does not list employers, dates, or a full project history in the excerpt available. Treat the "widely used" claim as his characterization, and use the dated posts and category list as the verifiable trail of what he has worked on and written about.