<story><title>Inverse Live Coding: A practice for learning web development</title><url>https://computinged.wordpress.com/2019/02/04/inverse-live-coding-a-practice-for-teaching-web-development/</url></story><parent_chain></parent_chain><comment><author>_57jb</author><text>Not meant to be an attack and possibly I am missing something but if I paid to take a course at a university and the person teaching it was only ever a step ahead of me at any time... I&amp;#x27;d have never taken the course.&lt;p&gt;This style of teaching (I feel) gives the illusion of confidence that the student is on the right track although its barely more than blind leading the blind.&lt;p&gt;Possibly an unpopular opinion but I have been tricked by folks like this in the working world and academia...I feel it is the source of much of my frustration with CS as a profession.</text></comment>
<story><title>Inverse Live Coding: A practice for learning web development</title><url>https://computinged.wordpress.com/2019/02/04/inverse-live-coding-a-practice-for-teaching-web-development/</url></story><parent_chain></parent_chain><comment><author>robert_tweed</author><text>This is a format that I&amp;#x27;ve thought for some time would work exceptionally well in technical interviews: rather than ask a bunch of questions, have a small set of problems that start from a working piece of code in need of work.&lt;p&gt;This removes some of the subjectivity from a completely open-ended coding assignment, as well as reducing the amount of effort required, because you can do a few small problems rather than a single huge one that typically involves working over a weekend.&lt;p&gt;The only downside is it&amp;#x27;s a lot more effort to set up than either an open assignment or a standard Q&amp;amp;A-based interview. You don&amp;#x27;t want to throw anyone into real production problems for a variety of reasons. The initial setup has to be understandable within a few minutes of code review.</text></comment>