Awesome email advice from a friend on how to learn programming.
Let's start with the first and most important rule of learning to code. Read everything and understand what you're reading. Do not skip or skim words or communication of any kind. Don't read something assuming you know what it means; if you don't understand it, look around, ask someone, or google until you understand what you've just read. Then, you can move on. The reason for this is that programming involves comprehension, not knowledge (more on that below). Failure to follow this will make you a sucky programmer. You'll write buggy code. You'll piss yourself off when you think nobody wants to help you. Then, you'll end up really pissed because everything you thought you knew how to do falls apart, and you finally realize you're a bad programmer. This happened to me about 7yrs ago -- so, I'm trying to save you the trouble. After I realized this, and, after I learned how to program, not
Why it failed
Let's start with the first and most important rule of learning to code. Read everything and understand what you're reading. Do not skip or skim words or communication of any kind. Don't read something assuming you know what it means; if you don't understand it, look around, ask s
- Kind
- startup
- Status
- Shut down
- Inventor
- nav
- Ended
- 2010
- Source
- hackernews