Communities

Writing
Writing
Codidact Meta
Codidact Meta
The Great Outdoors
The Great Outdoors
Photography & Video
Photography & Video
Scientific Speculation
Scientific Speculation
Cooking
Cooking
Electrical Engineering
Electrical Engineering
Judaism
Judaism
Languages & Linguistics
Languages & Linguistics
Software Development
Software Development
Mathematics
Mathematics
Christianity
Christianity
Code Golf
Code Golf
Music
Music
Physics
Physics
Linux Systems
Linux Systems
Power Users
Power Users
Tabletop RPGs
Tabletop RPGs
Community Proposals
Community Proposals
tag:snake search within a tag
answers:0 unanswered questions
user:xxxx search by author id
score:0.5 posts with 0.5+ score
"snake oil" exact phrase
votes:4 posts with 4+ votes
created:<1w created < 1 week ago
post_type:xxxx type of post
Search help
Notifications
Mark all as read See all your notifications »
Meta

Welcome to Software Development on Codidact!

Will you help us build our independent community of developers helping developers? We're small and trying to grow. We welcome questions about all aspects of software development, from design to code to QA and more. Got questions? Got answers? Got code you'd like someone to review? Please join us.

Post History

60%
+1 −0
Meta Should I delete my trivial, lack-of-research question?

I agree with the previous answers, don't delete a question that you find it looking trivial after you find the answer, instead answer it, and if it's possible, improve the question, i.e., by provid...

posted 11mo ago by Wicket‭  ·  edited 11mo ago by Wicket‭

Answer
#4: Post edited by user avatar Wicket‭ · 2023-06-24T16:34:48Z (11 months ago)
  • I agree with the previous answers, don't delete a question that you find it looking trivial **after** you find the answer, instead answer it, and if it's possible, improve the question, i.e., by providing relevant details about the context that might explain why you skipped what you be sharing in the answer.
  • IMO, only blatantly off-topic, "broken windows" and very badly received posts should be deleted. I understand that sometimes closed questions should be deleted when the OP doesn't know how to improve to question to be reopened or what was learned after posting the question leads to "rewrite" it as a different question.
  • If you already know the software development basics and faced challenges learning a new platform, SDK, etc. others might find your learnings helpful. Software development is a very broad topic and software developers have to be able to quickly catch the workings of platforms, methods, tools, etc. either because they are new or they are continually changing.
  • I agree with the previous answers, don't delete a question that you find it looking trivial **after** you find the answer, instead answer it, and if it's possible, improve the question, i.e., by providing relevant details about the context that might explain why you skipped what you be sharing in the answer.
  • IMO, only blatantly off-topic, "broken windows" (something that attracts bad posts, causing more harm than good) and very badly received posts should be deleted. I understand that sometimes closed questions should be deleted when the OP doesn't know how to improve to question to be reopened or what was learned after posting the question leads to "rewrite" it as a different question.
  • If you already know the software development basics and faced challenges learning a new platform, SDK, etc., others might find your learnings helpful. Software development is a very broad topic, and software developers have to be able to quickly catch the workings of platforms, methods, tools, etc., either because they are new or they are continually changing.
#3: Post edited by user avatar Wicket‭ · 2023-06-24T16:32:17Z (11 months ago)
  • I agree with the previous answers, don't delete a question that you find it looking trivial **after** you find the answer, instead answer it, and if it's possible, improve the question.
  • IMO, only blatantly off-topic, "broken windows" and very badly received posts should be deleted. I understand that sometimes closed questions should be deleted when the OP doesn't know how to improve to question to be reopened or what was learned after posting the question leads to "rewrite" it as a different question.
  • If you already know the software development basics and faced challenges learning a new platform, SDK, etc. others might find your learnings helpful. Software development is a very broad topic and software developers have to be able to quickly catch the workings of platforms, methods, tools, etc. either because they are new or they are continually changing.
  • I agree with the previous answers, don't delete a question that you find it looking trivial **after** you find the answer, instead answer it, and if it's possible, improve the question, i.e., by providing relevant details about the context that might explain why you skipped what you be sharing in the answer.
  • IMO, only blatantly off-topic, "broken windows" and very badly received posts should be deleted. I understand that sometimes closed questions should be deleted when the OP doesn't know how to improve to question to be reopened or what was learned after posting the question leads to "rewrite" it as a different question.
  • If you already know the software development basics and faced challenges learning a new platform, SDK, etc. others might find your learnings helpful. Software development is a very broad topic and software developers have to be able to quickly catch the workings of platforms, methods, tools, etc. either because they are new or they are continually changing.
#2: Post edited by user avatar Wicket‭ · 2023-06-24T16:30:09Z (11 months ago)
  • I agree with the previous answers, don't delete a question that you find it looking trivial **after** you find the answer.
  • IMO, only blatantly off-topic, "broken windows" and very badly received posts should be deleted. I understand that sometimes closed questions should be deleted when the OP doesn't know how to improve to question to be reopened or what was learned after posting the question leads to "rewrite" it as a different question.
  • If you already know the software development basics and faced challenges learning a new platform, SDK, etc. others might find your learnings helpful. Software development is a very broad topic and software developers have to be able to quickly catch the workings of platforms, methods, tools, etc. either because they are new or they are continually changing.
  • I agree with the previous answers, don't delete a question that you find it looking trivial **after** you find the answer, instead answer it, and if it's possible, improve the question.
  • IMO, only blatantly off-topic, "broken windows" and very badly received posts should be deleted. I understand that sometimes closed questions should be deleted when the OP doesn't know how to improve to question to be reopened or what was learned after posting the question leads to "rewrite" it as a different question.
  • If you already know the software development basics and faced challenges learning a new platform, SDK, etc. others might find your learnings helpful. Software development is a very broad topic and software developers have to be able to quickly catch the workings of platforms, methods, tools, etc. either because they are new or they are continually changing.
#1: Initial revision by user avatar Wicket‭ · 2023-06-24T16:28:34Z (11 months ago)
I agree with the previous answers, don't delete a question that you find it looking trivial **after** you find the answer.

IMO, only blatantly off-topic, "broken windows" and very badly received posts should be deleted. I understand that sometimes closed questions should be deleted when the OP doesn't know how to improve to question to be reopened or what was learned after posting the question leads to "rewrite" it as a different question.

If you already know the software development basics and faced challenges learning a new platform, SDK, etc. others might find your learnings helpful. Software development is a very broad topic and software developers have to be able to quickly catch the workings of platforms, methods, tools, etc. either because they are new or they are continually changing.