←back to thread

123 points eterm | 1 comments | | HN request time: 0.28s | source
Show context
eterm ◴[] No.43925356[source]
A post in which I try to rubber-duck a CoreWCF issue I've been having, because stackoverflow no longer seems suitable for asking questions about programming issues.

Screaming into the void of the blogosphere is catharsis for getting my SO question closed.

And because I know you're all nosy, the SO question is here: https://stackoverflow.com/questions/79605462/high-cpu-usage-... . Please feel free to point out more ways in which I screwed up asking my SO question.

replies(10): >>43925551 #>>43925669 #>>43925930 #>>43925975 #>>43926332 #>>43927351 #>>43931071 #>>43933405 #>>43933839 #>>43935803 #
the_clarence ◴[] No.43931071[source]
The same has happened on reddit a long time ago. Most users give up early because they get their forst posts (on any community) removed many times before they can manage (if they do manage) to post it. If the feedback loop was faster (you instantly get feedback on why the post doesn't go through) it would be better although you would already lose some users. The situation is so bad that I predict reddit is slowly dying already
replies(2): >>43931918 #>>43933339 #
1. socalgal2 ◴[] No.43933339[source]
this will no longer happen because everyone has learned to just ask the LLM who will just answer. No need for reddit or S.O. for tech questions