zlacker

[return to "Why users cannot create Issues directly"]
1. ok1234+Mh[view] [source] 2026-01-02 04:29:02
>>xpe+(OP)
100% agree.

If it's someone else's project, they have full authority to decide what is and isn't an issue. With large enough projects, you're going to have enough bad actors, people who don't read error messages, and just downright crazy people. Throw in people using AI for dubious purposes like CVE inflation, and it's even worse.

◧◩
2. Sohcah+XU1[view] [source] 2026-01-02 18:20:59
>>ok1234+Mh
> people who don't read error messages

One of my pet peeves that I will never understand.

I do not expect users to understand what an error means, but I absolutely expect them to tell me what the error says. I try to understand things from the perspective of a non-technical user, but I cannot fathom why even a non-technical user would think that they don't need to include the contents of an error message when seeking help regarding the error. Instead, it's "When I do X, I get an error".

Maybe I have too much faith in people. I've seen even software engineers become absolutely blind when dealing with errors. I had a time 10 years ago as a tester when I filed a bug ticket with explicit steps that results in a "broken pipe error". The engineer closed the ticket as "Can Not Reproduce" with a comment saying "I can't complete your steps because I'm getting a 'broken pipe error'".

◧◩◪
3. mamcx+kg3[view] [source] 2026-01-03 04:43:26
>>Sohcah+XU1
My theory is that the best, absolute best predictor if someone could be a good programmer (or is) is the ability to read exactly what is written.

Is not math, logic or any of that asides. Is the actual ability to read, exactly, without adding or removing anything.

◧◩◪◨
4. latexr+C04[view] [source] 2026-01-03 12:20:15
>>mamcx+kg3
You can test that theory with Magic the Gathering players. Reading exactly what the card says and interpreting it with the exact text of the rules is core to the game.
[go to top]