DEV Community

Discussion on: 10 must follow rules for asking coding questions

Collapse
 
mccurcio profile image
Matt Curcio

I have spent a fair amount of time "grading" (or reviewing) first time posts on Stackoverflow and find one item VERY important.

  • Giving a reproducible example is one piece of advice I notice above all. Without reproducible examples many problems cannot be solved or troubleshot.
  • Giving a reproducible example may mean having a small data set. Even having x = [1,2,3] may set the ground work if you have input or output issues.
  • Having a complete minimal example is very useful too. If one can whittle down the possibilities then life is easier for everyone involved.

I also cite something similar to this post often: How to ask a good question

Collapse
 
allthecode profile image
Simon Barker

Great points, in this case I am thinking more around asking people directly on your team but certainly if it was more async like SO is then a reproducible example is a must 😀

Collapse
 
mccurcio profile image
Matt Curcio

Absolutely, I should have just come out first and said I agree with your points.
But in the circumstance where one does not have access to a great team... haha.

I might add two more point to the 'Still Stuck' section.

  1. Go walk around and get the blood flowing. (to your head again haha) or another favorite,
  2. Move on to something new. Don't get caught in the death spiral. Keep going don't loose your momentum.
Thread Thread
 
allthecode profile image
Simon Barker

I really should go for a walk more often when I'm stuck - I just get sucked in to the problem

Thread Thread
 
mccurcio profile image
Matt Curcio

Yea, I get sucked in too.
Some people I know swear by Pomodoro method bc it forces one to walk or at least get up but I find 25-30 min is just too short.