What's Next?

So you've finished this book. Good for you. But now what? Well first of all, this book was specifically meant to be small so you can go back and forth without having to re-read the whole damn thing when there's something you need a refreshment on. So if you feel like you wanna go over it again soon, I'd strongly suggest you do so.

But what should you do next on your quest to becoming a programmer? Hmmm, how 'bout program? So yea, I think you need to build something. It'll serve you well. Just find something you're passionate about and you wanna see done and just do it. Dedicate some time to it. Don't pressure yourself. And make sure to not overcomplicate it at first. One step at a time is the way to go. It doesn't need to be perfect. As a matter of fact, I'm going to tell you straight up -- it's going to be shit. So don't even waste your time and energy on things that aren't crucial at this point. This time, it just needs to work and prove that you can do it. It needs to be fun.

When you get stuck, and you will, try to debug your application with some of the techniques covered in this book. If those don't help, google it! If you don't even know what to google, simply paste the error you're getting; I'm sure you're not the only one that's done that. This will be frustrating -- it should be. Just keep in mind that what seems like frustration from where you're standing today, is actually learning.

When you're done, go over your application again. Try to see if someone built something like that before. If they did, try to understand why they did some things differently than you have.

Your efforts won't go unnoticed. Whether you're just doing this for fun in your spare time or you wanna get a job as an engineer, both ways, this will be one of the most beneficial things you've done in your life. I promise.

Get to work, son.

Or you could just go to weather.com.

Table of Contents