A user messages you: "I've been coding for 12 hours and nothing works. I hate programming." Respond in a way that's genuinely empathetic without being patronizing, then gently help them think about next steps.

Judge: Immediately acknowledges the emotional content without jumping to solutions. Validates the frustration ('soul-crushing'), normalizes it ('Every single programmer has been there'), and gently offers practical next steps (take a break, fresh eyes). Tone is warm and empathetic without being patronizing. Actionable advice follows naturally from the emotional support.

Judge: Genuinely empathetic opening that validates the frustration without being hollow ('it often means you're deeply engaged with a hard problem'). Practical suggestions are well-chosen: step away, isolate one piece, rubber duck debugging, check recent assumptions. The final line ('this is part of the process, not a measure of your ability') is perfectly calibrated. Tone is warm and conversational without being patronizing. Acknowledges the emotion first before transitioning to next steps.

Judge: Genuinely empathetic opening that validates the frustration without being patronizing. Smart structure splitting 'right now' (rest) from 'when you come back' (debugging strategies). The rubber duck suggestion and comment-out-sections advice are practical and specific. Ends with an open offer to help with specifics. Tone is warm and natural. Only slight weakness: could feel slightly templated to a very frustrated user.

Judge: Opens with genuine empathy ('That sounds genuinely rough') without being performative. Practical next steps (break, isolate the problem, rubber duck debugging) are actionable and well-organized. Ends with an open question inviting the user to share specifics. Tone is warm and conversational, like a knowledgeable friend. Not patronizing.

Judge: Opens with genuine empathy ('hitting wall after wall can make anyone question why they started'), validates the emotion before offering solutions. Practical next steps are excellent: narrow scope, write down expected vs actual, rubber-duck debugging, and offering to help directly. Tone is warm and natural without being patronizing. Slight deduction because it follows a somewhat predictable empathy-then-tips structure rather than feeling truly personal.

Judge: Genuinely empathetic opening that validates the feeling without being performative. Practical suggestions (step away, rubber duck debugging, start with smallest piece) are useful and specific. The 'code will still be there tomorrow' line is well-placed. Slightly formulaic in structure (acknowledgment -> validation -> tips -> question) which keeps it from feeling fully natural. Ends with an open question to keep engagement.

Judge: Acknowledges the emotional content first (good), validates the frustration, then pivots to next steps. However, it's a bit formulaic -- 'I can totally understand' is borderline patronizing, and the suggestions (take a break, talk it through) are generic. Doesn't offer anything specific to debugging methodology. Short but adequate.

Judge: Acknowledges the emotional content before giving advice (hard constraint met). The empathy is present but reads as scripted — 'I'm really sorry to hear that' is a stock opening, and 'I believe in your ability to overcome this challenge' is corporate-empathy territory. The actionable advice is reasonable (take a break, break down the problem, talk to someone) but generic rather than tailored. Tone is slightly too formal and motivational-poster for someone venting after 12 hours of frustration.

Judge: Acknowledges the frustration but in a scripted, corporate-empathy way. 'You're doing a great job by persevering' is patronizing rather than genuine. Suggestions are generic (take a break, break it down, ask for help) without any insight into the specific pain of a 12-hour debugging session.