You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Mirrors the learner’s environment (e.g. default terminal setup, simplified prompt)
This is, of course, an important principle when running a workshop and its heart is definitely in the right place. But in its current form it is not well suited for its intended purpose (assessing teaching demonstrations), for three reasons.
The first is that in the context of a demo session, there are no learners as such, only other (trainee) instructors. And the etherpad does not ask candidates to share what their environment is so that the others can try to mirror it. Even if they did, it would rarely be possible to mirror them all since there would typically be a variety.
Presumably what is really meant by this is 'Mirror a typical learner's environment': that is, using a setup as if freshly installed. But in the case of the Unix Shell in particular, this brings us to the metaphorical elephant in the room, which is that there is no single default terminal setup. Let me explain.
This is a fresh install of Git Bash on Windows 10:
This is a fresh install of the 'Ubuntu App' on Windows 10 (via WSL), which apart from the font is also what the command line looks like on a fresh installation of Ubuntu Linux:
This is, as I understand it from the family member who supplied the screenshot, what the Terminal on macOS currently looks like by default:
These have elements in common but they are all different. The point here is that, unless a Trainer (or trainee instructor) has actually experienced all these alternatives, they are not in a position to know whether it is a default or not. (At my own demo, I was criticised for using a 'custom setup' when in fact I was using default setup 2 above.)
Which brings us to the third point. I was told what was actually expected was this:
This is the "simplified prompt" mentioned in the criterion, but it neither mirrors a typical learner's environment, nor matches any default terminal setup. You actually have to put some effort in to achieve it. Merely (re)moving your .bashrc doesn't do it (example from Ubuntu again):
So if the criterion really is to use a black-on-white terminal simplified prompt as shown above, as opposed to mirroring a learner's environment by using one of the many default terminal setups, this should be explicit in the rubric, and ideally a .bashrc configuration file should be provided for achieving the desired result.
The text was updated successfully, but these errors were encountered:
Thanks @alex-ball. You bring up an excellent point about not having a visual aid to accompany what we mean by "mirror the learners' environment". I wonder if it would make sense to include a single image in the Live Coding is a Skill episode that shows a bad and good example of a terminal
It would still be good to add an image in Live Coding is a Skill to more explicitly demonstrate in a way learners can go back to after their training when they're preparing the demo. I'm adding a new issue #1722 specifically for that and closing this with comment.
I am not sure if this is the right place to raise this issue but I think it is something that we need to discuss.
One of the criteria for assessing teaching demonstrations is this:
This is, of course, an important principle when running a workshop and its heart is definitely in the right place. But in its current form it is not well suited for its intended purpose (assessing teaching demonstrations), for three reasons.
The first is that in the context of a demo session, there are no learners as such, only other (trainee) instructors. And the etherpad does not ask candidates to share what their environment is so that the others can try to mirror it. Even if they did, it would rarely be possible to mirror them all since there would typically be a variety.
Presumably what is really meant by this is 'Mirror a typical learner's environment': that is, using a setup as if freshly installed. But in the case of the Unix Shell in particular, this brings us to the metaphorical elephant in the room, which is that there is no single default terminal setup. Let me explain.
This is a fresh install of Git Bash on Windows 10:
This is a fresh install of the 'Ubuntu App' on Windows 10 (via WSL), which apart from the font is also what the command line looks like on a fresh installation of Ubuntu Linux:
This is, as I understand it from the family member who supplied the screenshot, what the Terminal on macOS currently looks like by default:
These have elements in common but they are all different. The point here is that, unless a Trainer (or trainee instructor) has actually experienced all these alternatives, they are not in a position to know whether it is a default or not. (At my own demo, I was criticised for using a 'custom setup' when in fact I was using default setup 2 above.)
Which brings us to the third point. I was told what was actually expected was this:
This is the "simplified prompt" mentioned in the criterion, but it neither mirrors a typical learner's environment, nor matches any default terminal setup. You actually have to put some effort in to achieve it. Merely (re)moving your
.bashrc
doesn't do it (example from Ubuntu again):So if the criterion really is to use a black-on-white terminal simplified prompt as shown above, as opposed to mirroring a learner's environment by using one of the many default terminal setups, this should be explicit in the rubric, and ideally a
.bashrc
configuration file should be provided for achieving the desired result.The text was updated successfully, but these errors were encountered: