What Is Joseph Mate's Website (josephmate.github.io)?

Updated

josephmate.github.io is the personal technical blog and project site of Joseph Mate, a software engineer. It publishes long-form write-ups about debugging hard production problems and building developer tools, and it links out to his GitHub and LinkedIn profiles. It is not a product site: there is no pricing, signup, or commercial offering described on it.

What you'll find there

The site is organized as a stream of posts, each built around a single technical problem or project. From the published headings, the content falls into two rough categories.

Performance and debugging investigations

  • Ghost in the Wi-Fi — a debugging narrative that opens with the author deep in a flow state, wrapping up a pull request, only to be interrupted by an Outlook meeting reminder. The framing suggests a bug hunt that spans more than one sitting.
  • 3,200% CPU Utilization — a case where reported CPU usage exceeds what a single core should be able to produce, which usually points to how utilization is being measured or aggregated rather than to a literal 32 cores of work.
  • 1,000,000 Concurrent Connections — a scale problem, typically about file descriptors, kernel limits, memory per connection, or accept-loop design.
  • 100% CPU: My Fault? — a post that questions whether the author's own code is responsible for a CPU spike.

Developer tooling

  • OdinCodeBrowser: Navigate Code Like in your IDE but on a Static Webpage — a project write-up about bringing IDE-style code navigation (jump to definition, find references) to a page that is served as static files, with no backend.

Who it's for

The site suits readers who want first-hand accounts of production debugging rather than tutorials: engineers dealing with resource-exhaustion bugs, capacity limits, or profiling data that doesn't add up, and people interested in how far static web pages can be pushed toward IDE-like functionality.

It is less useful if you are looking for API documentation, a library you can install, or a service to sign up for. The posts read as experience reports and project notes.

How to use it

  1. Open the site and scan the post headings — they are descriptive enough to pick by symptom (high CPU, connection limits) or by project name.
  2. Read the debugging posts for method rather than for a copy-paste fix: the value is in how the problem was narrowed down, not in a universal solution.
  3. For the OdinCodeBrowser post, treat it as a design explanation of a static-page tool.
  4. Follow the GitHub link if you want source code or to check whether a described project is maintained; follow LinkedIn for professional background.

What it is not

There is no evidence on the site of paid content, subscriptions, or a product with a price. Nothing indicates whether any linked repository is open source, so check the individual repository if licensing matters to you. The posts are written in English.