Never underestimate the value of stepping away from the problem and coming back in a while. All the answers in this thread so far are on point. Since we're on dev.to, I'll add that this is the type of case we are trying to tackle with this site/community. @codemouse92
and others have requested chat-oriented stuff in the past and we're definitely listening but trying not to spread ourselves too.
I had a good phone call the other day with my brother @mikeydorje
, who has become a self-taught developer and we had a really productive chat about where to go on a project to work through the current issues. I've had a few similarly productive times in the past that lead to great aha moments and solutions. It's certainly easier to cover a lot of ground with a junior-but-not-too-junior developer than folks with more specific advanced needs but we're really motivated to keep working on the little things which can result in a lot more aha moments.
Anyway, my 2 cents about what goes through my head when this type of thing comes up.
P.S. I happened to see that @dmfay
was the Stack Overflow answerer on a question that helped me out. Fun to see familiar profile pics across the web. 🙂
I have an idea: a frustration button. I'll sell a big red USB connected button.
Press it once/lightly and all your code is marked read-only for 30 minutes.
Press it twice, or hard, and your github privileges are removed for the day, and your browser blocks all coding URLS.
Smash the button and your project is completely locked until you manage to get a first-page posting on /r/earthporn.
I help out a lot in my classes and am helping in an intro class this semester. I think a few of the students thought I was kidding, but I totally told them that when I get to a Certain Level of frustrated, I zip up the whole thing, email it to a friend and save a copy on Google Drive or wherever. (Also basic versioning stuff.)
Then no matter how pissed or frustrated I get, if I get to the Very Dangerous Spot of "Screw this I'm deleting all of it" (after which, inevitably, ten minutes later you remember the One Thing that would have fixed it) there are copies you literally could not destroy.
...I also got so frustrated at an assignment last semester that I literally wrote a script locking me out of the cloud-based editor we were using, and ended up having so much fun locking myself out that it cured my bad mood until I actually got to office hours to ask the teacher the next day.
Well, I'm glad that I'm not the type of person who deletes all of my work when I get mad, I just abandon it
Great phone call @ben
. I'll be posting some thoughts, questions, and whatnot about what I'm working on when I have some free time.
We're a place where coders share, stay up-to-date and grow their careers.
We strive for transparency and don't collect excess data.