It’s too easy to get behind in exercises, or to completely get stuck.

[jacobsee]

Problem:
Explore the best way for learners to quickly catch up when they get behind or make a mistake that is hard to find / recover from. I think we can agree that spending a lot of time digging into a bracket or indentation error is not the best way for attendees to spend their time.

Proposed solution:
Initial implementation could be as simple as “this is what your code should look like”. Further, reference git branches & instructions on how to pull them. Full implementation could be a script or task to run in CRW that pulls and merges a reference branch.