What Topics Does Joseph Mate Write About on josephmate.github.io?

Joseph Mate's site (josephmate.github.io) is a personal engineering blog built around debugging war stories and developer tooling. The visible post titles cluster into two groups: deep dives into production performance mysteries (Wi-Fi behavior, runaway CPU usage, massive connection counts) and a project write-up for a code-browsing tool. If you want first-hand accounts of tracking down hard bugs rather than introductory tutorials, this is the kind of site worth reading.

Performance debugging and production incidents

The strongest signal from the page is a set of posts framed as investigations into systems behaving badly:

• "Ghost in the Wi-Fi" — the excerpt describes being deep in a flow state, wrapping up a fix in a pull request, when an Outlook meeting popup interrupts. The framing suggests a bug that was elusive or intermittent, the kind that resists obvious explanation.
• "3,200% CPU Utilization" — a title that implies CPU usage far beyond a single core, pointing to multi-threaded or multi-process contention rather than a simple busy loop.
• "1,000,000 Concurrent Connections" — a scale-focused post, likely about what breaks when connection counts reach extreme levels.
• "100% CPU: My Fault?" — a question-form title that signals the author questioning whether the load was self-inflicted, a common moment in performance work.

Taken together, these read as postmortem-style write-ups: a symptom appears, the cause is non-obvious, and the resolution is documented. The excerpt's detail about writing up the report in a pull request confirms the author works from real code changes, not hypothetical scenarios.

Developer tooling and side projects

One post sits outside the debugging theme:

• "OdinCodeBrowser: Navigate Code Like in your IDE but on a Static Webpage" — this describes a project that brings IDE-style code navigation to a static web page. It's a tool announcement or walkthrough rather than an incident report.

This matters if your interest is in how to make code readable and navigable without a full IDE or backend. It also shows the site isn't purely reactive debugging content; the author builds things too.

What kind of reader gets value here

The common thread is the author's own hands-on experience: the excerpt is written in first person, mid-task, describing a bug and a pull request. That style suits readers who learn from someone else's debugging process rather than from reference documentation.

How to decide whether to read it

Start with the post whose symptom matches a problem you're facing. If you're chasing unexplained CPU spikes, the "3,200% CPU Utilization" and "100% CPU: My Fault?" posts are the natural entry points. If you're dealing with connection scaling, the million-connections post is the relevant one. If you're interested in code navigation tooling, go to the OdinCodeBrowser write-up.

One caveat: the page evidence shows titles and a short excerpt, not full article contents, so the depth and technical specificity of each post can only be judged by opening it. The titles and framing are consistent with detailed engineering write-ups, but treat that as an expectation to verify, not a guarantee.