Oh, I can definitely see how that's good. For programming, though, I disagree slightly. You shouldn't stop immediately. Programming is a form of problem-solving, after all. Nothing would ever get solved if people stopped straight away whenever they came up against a wall.
Sure, you shouldn't just bang your head against that wall and get nowhere, but before you go, check if there's a door you could find a way through. Usually, if I'm stuck I spent a bit of time trying out different fixes and googling to see if others have encountered the same issue. If I'm clearly getting nowhere or just wasting time, I go do something else for a couple of hours, then try again. It's only then, if I'm still not making any headway, that I leave programming alone for the rest of the day.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Oh, I can definitely see how that's good. For programming, though, I disagree slightly. You shouldn't stop immediately. Programming is a form of problem-solving, after all. Nothing would ever get solved if people stopped straight away whenever they came up against a wall.
Sure, you shouldn't just bang your head against that wall and get nowhere, but before you go, check if there's a door you could find a way through. Usually, if I'm stuck I spent a bit of time trying out different fixes and googling to see if others have encountered the same issue. If I'm clearly getting nowhere or just wasting time, I go do something else for a couple of hours, then try again. It's only then, if I'm still not making any headway, that I leave programming alone for the rest of the day.