<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Wouter Nederhof on foojay.io - Friends of OpenJDK</title><link>https://foojayio.github.io/website/today/author/wouter-nederhof/</link><description>Articles written by Wouter Nederhof on foojay.io - Friends of OpenJDK</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Mon, 13 May 2024 07:11:04 +0000</lastBuildDate><atom:link href="https://foojayio.github.io/website/today/author/wouter-nederhof/index.xml" rel="self" type="application/rss+xml"/><item><title>Diagnosing user-reported issues using WireQuery</title><link>https://foojayio.github.io/website/today/diagnosing-user-reported-issues-using-wirequery/</link><pubDate>Mon, 13 May 2024 07:11:04 +0000</pubDate><guid>https://foojayio.github.io/website/today/diagnosing-user-reported-issues-using-wirequery/</guid><description>&lt;p&gt;&lt;strong&gt;As a developer, I&amp;rsquo;ve often struggled with diagnosing user-reported issues, which is often caused by a lack of information to reproduce the problem. While a ticket may contain a screenshot of the problem and a description, it often does not portray the complete picture. For example: what did the user do that led up to the issue? What endpoints were called from the frontend, and how did they respond? What did the underlying systems communicate? Etc.&lt;/strong&gt;&lt;/p&gt;</description></item></channel></rss>