I’m seeking a website where I can ask any programming or tech-related questions without the risk of it being closed. The platform should allow linking of similar problems for better organization. Previously, I found HeapOverflow to be useful, but unfortunately, it is no longer available. Another platform I tried was Wotas.net (Wisdom of the Ancient Souls Q&A Tech Website), but it didn’t last long either. These platforms were not very active, often leading me to post solutions to my own questions. Despite this, I prefer them over websites with an army of moderators trying to find any excuse to close your post. My preference leans away from platforms like StackOverflow or Codidact, which focus mainly on bug-related questions. When dealing with troubleshooting bugs involving Minimal Reproducible Examples and error logs, I find seeking help from an LLM more beneficial than those kinds of websites anyways, due to their clear and concise responses.
I used to spend a ton of time helping people on reddit with linux and related things, and the “why” matters immensely in that case.
XY problem was extremely common, where someone was trying to achieve a goal through “incorrect” means.
I also saw many, many people’s issues where they wanted something, but were referring to it by a different name, ending up confused and lost. All I had to do was say “you actually want Y” and point them on their way, and they would be happy.
And then of course, sometimes people try to do something that’s simply not possible (or more usually, not implemented in software.).
But in general, it’s very difficult to help people who don’t make it easy for you to help them, and part of that is explaining the “why”, in addition to their issue.
I also contribute to communities like stackoverflow. There are very few reasons to ask “what are you trying to do”. Often it’s when the solution to their question doesn’t help them reach their actual goal and they willingly say “actually, I was trying to do X, but this didn’t achieve that”. Other cases are when they ask things like “why doesn’t this work” or “could you recommend ABC” and don’t provide enough information to answer the question.
An example “how do I fit this $lightbulb into $fitting” shouldn’t be answered with “why?” even if you first thought is “that makes no sense, why would you do that?”. Maybe they don’t have other lightbulbs or fittings, maybe that fitting is the only one with a potentiometer or transformer they could find, maybe they actually bought the wrong fitting.
IMO, a better answer is “I would advise against it, but here’s how I would do it”. It’s then up to the person asking the question to either indicate that they want to know why you advise against it, try it out and find out that it works for them or doesn’t. You asking “why” might just waste their time having to explain circumstances and wait on async responses instead of just getting a solution and deciding for themselves whether it helped or not.
“Why” is often a waste of time and prone to tangents.I try not provide context to my questions anymore because of that.
You are not logged in. However you can subscribe from another Fediverse account, for example Lemmy or Mastodon. To do this, paste the following into the search field of your instance: !programming@programming.dev
Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!
Cross posting is strongly encouraged in the instance. If you feel your post or another person’s post makes sense in another community cross post into it.
Hope you enjoy the instance!
Rules
Rules
Follow the programming.dev instance rules
Keep content related to programming in some way
If you’re posting long videos try to add in some form of tldr for those who don’t want to watch videos
I used to spend a ton of time helping people on reddit with linux and related things, and the “why” matters immensely in that case.
XY problem was extremely common, where someone was trying to achieve a goal through “incorrect” means.
I also saw many, many people’s issues where they wanted something, but were referring to it by a different name, ending up confused and lost. All I had to do was say “you actually want Y” and point them on their way, and they would be happy.
And then of course, sometimes people try to do something that’s simply not possible (or more usually, not implemented in software.).
But in general, it’s very difficult to help people who don’t make it easy for you to help them, and part of that is explaining the “why”, in addition to their issue.
I also contribute to communities like stackoverflow. There are very few reasons to ask “what are you trying to do”. Often it’s when the solution to their question doesn’t help them reach their actual goal and they willingly say “actually, I was trying to do X, but this didn’t achieve that”. Other cases are when they ask things like “why doesn’t this work” or “could you recommend ABC” and don’t provide enough information to answer the question.
An example “how do I fit this $lightbulb into $fitting” shouldn’t be answered with “why?” even if you first thought is “that makes no sense, why would you do that?”. Maybe they don’t have other lightbulbs or fittings, maybe that fitting is the only one with a potentiometer or transformer they could find, maybe they actually bought the wrong fitting.
IMO, a better answer is “I would advise against it, but here’s how I would do it”. It’s then up to the person asking the question to either indicate that they want to know why you advise against it, try it out and find out that it works for them or doesn’t. You asking “why” might just waste their time having to explain circumstances and wait on async responses instead of just getting a solution and deciding for themselves whether it helped or not.
“Why” is often a waste of time and prone to tangents.I try not provide context to my questions anymore because of that.
But you do you.
CC BY-NC-SA 4.0