I've been involved with one of them.<p>1. I don't know which one you'll be joining, but do the prepwork.<p>2. If the prepwork doesn't include git, learn git (Recommend CodeSchool, GitHub's tutorial, and generally spending time using git). Reading Pro Git or something like that doesn't really help unless you've been using git for a while. Learn how to use GitHub (fork, cloning, pull requests, issues, etc). Build a good internal mental model for what is going on.<p>3. Get in the habit of <i>properly</i> touch-typing if you don't already (meaning all ten fingers and using the pinky). You'd be surprised how even a lot of programmers don't properly touch type. Get comfortable with a standard text editor (I recommend Sublime Text for a beginner. You can learn vim later, maybe after the course).<p>4. If the course curriculum does not include <i>basic</i> data structures and algorithms, get a good overview of basic data structures and algorithms. Meaning learn about hashes, arrays, multi-dimensional arrays, stacks, queues, linked lists, trees, binary search trees and how to implement them. Learn about order of growth, etc. If the course does cover those topics, then you can go ahead and hold off on learning them (or not). You <i>can</i> read about these topics, but I think getting it explained to you by a teacher, assuming those topics are covered in the course, is a lot easier and intuitive.<p>5. Some courses don't go into much depth about HTML and CSS (for good reason - those topics are just pure memorization, lots of busywork and trial and error, not very much educational value). If so, brush up on HTML and CSS, especially advanced CSS. A lot of web dev interviews will (sadly) involve those two areas.<p>6. Code as much as possible. Jump ahead. Read as much as possible. If it's a Rails school, take the initiative to go through the Hartl tutorial, learn/read/code about advanced Ruby metaprogramming. Ditto if you're doing JS or Python.<p>7. Start a personal website and blog. Make it look good (this can be your practice for #5). This is not important for success in the course, but is important for branding yourself after the course. By the way, I personally believe you should avoid branding yourself as a "junior" developer. Avoid that.