Ok, style for the actual class: We start the day out with a code challenge, then move into a mini lecture (a few students with one instructor) and a mini project you'll work on with a pair programming partner. Then another short lecture and you'll begin working on your main project.
If you're ever stuck you jump onto our #help channel on Slack and there's instantly someone available to help out. Chances are they've seen that problem before.
Once you're finished with your challenge or project you'll submit it as a pull request (we use Github for everything) and you'll have a code review. Sometimes those are in person, sometimes they're just comments left on code.
We have frequent brown bag lectures (lectures with industry experts) and office hours with instructors to discuss, well, anything.
Thanks for getting back to me. It sounds a bit geared towards people who have enough experience to know what to ask, so I'm not sure if this is something I would recommend to someone coming from a completely different field. Would that be an accurate assessment of the learning style?
Also, I'm still unsure about what tools will be used as part of the lectures. If it's really just screencasting + chat, I can't believe that the material will be conveyed all that well. At least as evidenced by how prepared your instructors seemed in the Archive videos. Sorry if it's a bit harsh, but my expectations are a bit high since I'm coming from a background that includes 5 years of teaching ESL.
If you're ever stuck you jump onto our #help channel on Slack and there's instantly someone available to help out. Chances are they've seen that problem before.
Once you're finished with your challenge or project you'll submit it as a pull request (we use Github for everything) and you'll have a code review. Sometimes those are in person, sometimes they're just comments left on code.
We have frequent brown bag lectures (lectures with industry experts) and office hours with instructors to discuss, well, anything.
Hope that helps!