I just completed my second week of Java bootcamp at Tech Elevator. This week we learned more data structures than I thought my brain could handle a...
For further actions, you may consider blocking this person and/or reporting abuse
The wording is a great help in debugging and continuing a stalled train of thought: describe the problem as if you were looking for a stranger with it who is absolutely unfamiliar with the circumstances, articulate the purpose of the task, how it works, and what can cause trouble. The more detailed you are about the problem, the more likely you are to come up with a solution without the help of others, and if you don’t figure it out yourself, you can actually ask the question on a forum.
Also use words for planning. UML diagrams and similar brainstorming solutions can help, but you only really see the task in full, in detail, if you describe the operation, because you are already thinking about possible mistakes and pitfalls while writing. If you read back your previous thoughts while writing, your brain won’t “short-circuit,” meaning you won’t get into the same train of thought over and over again.
Great advice!
What Jeff and others achieved this week was substantial. Every day we give double digit complex algorithmic problems to brand new developers. This is at its most intense from Thursday of week 1 to Thursday of week 2. Just getting through it is a feat, and coping strategies are mandatory. It is a good, good program, and as you go through what Jeff has this week, you emerge stronger, smarter, more capable, and ready to appreciate the complexities of larger applications and object oriented programming. All of this to say: Jeff knows what he's talking about.
Thanks Matt!!
Nicely written post !!
I've read online that in Bootcamps, the learning is pretty quick and intensive.
I'm learning to code on freeCodeCamp, whenever I get stuck, I try freeCodeCamp's forum, where you get a response within a couple of minutes, I google sometimes & when it can be discussed quickly I ask on freeCodeCamp's discord channel.
I simply camping myself with
PlayStationfor days. Ormountain-bikingand bring along a laptop in my backpack. Sometimes fresh air and earthy smell stimulate my creativity... lolThat’s a great idea! I haven’t had the chance to do any work outside yet but I can see how that would be beneficial
If I get frustrated while coding I better take a break and came back to code after refreshing my mind either by going out or talking with friends. After returning to code I might find solutions on web and I can easily learn and apply those changes to my code. Take a break is quite important step in this process.
I try to remember what I read in this short book(let) by James Webb Young - brilliant. Read the comments for a general idea, but it's not a long book at all (maybe 30 pages).
I wrote a bit about it here.
In a more specific sense, I find refreshing my function and argument types or a quick flow-diagram in whimsical help.
Besides all the above and its variants I will sometimes write a blank page new algorithm as a code sketch in a completely different language from the implementation language. Or in a made up DSL that seems to fit the problem. This can often get me moving again by casting the problem differently instead of banging my head against the same wall.
Taking a break seems to be a good solution. I listen to music, eat something maybe play a game and then come back to it. Usually I figure out a solution shortly after.
I totally ask for help. Or maybe look hard and hard for alternatives. And when I see no way out, I start crocheting! Reading a book also helps me.