Presented September 2014
print "hello world"
There, now we've started with code.
Now, let's back up.
But you're still going to sit through it.
Me: There is no right answer for a lot of what we do. You have to make an answer of your own and explain it.
Him: Don’t you feel freaked out by not knowing what the answer should be?
Me: Don’t you feel restricted by there only being one answer?
The higher we get in our home domains, the more that methodology seems to become a part of us and how we see the world.
Suggested steps for debugging:
Should you know?
Planning how you will do something is often impossible.
Focus more on planning that you will do something rather than what you will do.
Types of reference works
This will depend on why you are learning how to program.
I guarantee there will be other tools and structures you'll need to learn.
Make a list for when you need a break.
Text processing stack:
Or, how I learned to stop worrying and finish debugging my code.
You will feel lost, frustrated, and confused. Never, ever feel bad about feeling those things.
Learning curves are hard.
It gets better.
Then it gets awesome.
Take breaks and stare into space. Find your happy place.
Try rubber duck debugging.
(such under development. so in progress.)