Who else freaks out when they code and cannot find why the program doesnt work😪😪

Question

no pain no gain🏆

Answer 1

Given the lack of debugger available for SoloLearn code, my trick is lots of output lines. Displaying status as the program runs lets you know where it fails. Seeing values of your variables points out problems quickly. You can limit the output by counting how many times you get to the area and outputting every 20 or other number that makes sense. In 15 minutes, I've found a bug that occurred on the 56 call to a function using this technique and displaying the local variables only for the call to see the problem.

Answer 2

compiler and debbuger are very helpful in that situation 😁

Answer 3

u have to take rest and back to code and then u can see where is the problem it's happen

Answer 4

Definitely agree with taking a break. It always seems to work when you approach it with a fresh perspective. Also, debugging with breakpoints is a great way to hone in on that pesky problem.

Answer 5

Walk away take a walk outside do other things hell even sleep on it. Give your mind a break to collect your thoughts also make sure your hydrated and patient.

Answer 6

I clear my head for a few minutes , then I
do it the old fashioned way. I use a series of
print statements on variables that I suspect
are not working. That way I can see what is
taking place with the variables. I can see
the output of the suspected variables.
If that doesn't work I take a break for a
few hours , then look at the program from
a fresh perspective. If nothing else works
then I go do a Google search to see if
there is a similar problem solved.

Answer 7

thank you everybody, love the advice❤