User blames the compiler for a classic syntax error
Description
This image is a screenshot of a one-star review on an app store for an application named 'C/C++ Program Compiler'. A user, Jrmarion510, has posted a snippet of a basic C++ 'hello world' program, which contains a syntax error: the line 'include <iostream>' is missing the '#' prefix. The user complains, 'Does not run. I just get error messages.' Below the review, there is a patient 'Developer Response' from two years prior, which correctly points out the user's mistake: 'Hello, you are missing a # at the start. It should be #include instead of include . The error messages are meant to show errors in your codes; they are not a malfunction of the app.' The humor is derived from the user's misplaced blame, a situation highly relatable to experienced developers who often encounter bug reports that are actually user errors. It's a classic example of a beginner's mistake and the Dunning-Kruger effect in programming
Comments
14Comment deleted
Compilers are the ultimate code reviewers; they have zero patience for your feelings and a 100% success rate at finding your typos
One-starring the C++ compiler because you forgot the ‘#’ in #include is basically opening a Sev-0 on Kubernetes because your YAML isn’t indented - pure Layer-8 latency
After 20 years in the industry, you realize the most challenging bug to fix isn't in production code - it's convincing users that compiler error messages are features, not bugs. This is like leaving a 1-star review for grep because it 'keeps showing me lines with errors in them.'
The eternal struggle: a compiler that correctly identifies syntax errors gets a 1-star review because the error messages are 'working as intended.' This is the mobile development equivalent of a user reporting 'keyboard broken' when Caps Lock is on. The developer's patient response explaining that '#include' requires the '#' is a masterclass in technical support diplomacy - resisting the urge to reply with 'PEBKAC: Problem Exists Between Keyboard And Chair.' At least they didn't try to compile it with 'import <iostream>' or demand the app support 'include <iostream.h>' because 'that's how my 1998 Turbo C++ book showed it.'
Error messages as features? That's the kind of 'innovative' DX that makes senior devs nostalgic for edlin.exe
A one‑star because the compiler rejected 'include' without '#': the C++ version of filing a Sev‑1 that says, 'Monitoring is broken - it’s correctly reporting my bug.'
Review: “include <iostream>” doesn’t run. Support: “you forgot the #.” The future of C++ monetization - preprocessor as an in‑app purchase, modules on the enterprise tier
⭐️☆☆☆☆ Comment deleted
Imagine every error in your code being malfunction of the app Comment deleted
I bet it's that kind of person that has 20 avatars on telegram spelling stuff like "#CODE", "null", "void();" Comment deleted
Programming in python: print ('Hello World') Comment deleted
When StackOverflow is just not enough Comment deleted
Lmao Comment deleted
An app which blows your battery instead of raising an error Comment deleted