Wrap-up: what do we know now?
Thursday, 27 July 2017
Today we are going to wrap up the class and talk about the skills that you are taking away from this experience.
This information will be useful in the context of preparing a resume/CV or perhaps in conducting a job interview in which you are asked to talk about technical skills.
Skills and tools
I asked the class to identify the major skillsets that we engaged in learning this semester and recorded the output on the whiteboard.Students listed the skillsets they thought they had been exposed to.
I then followed this request by linking those skillsets to the tools used in engaging them. The images represent the output from this discussion.Students also listed the tools used in engaging those skillsets.
Following this, I talked briefly about how these skillsets might be engaged by other SILS courses and tried to link them accordingly. These courses are either related directly to the skillset or they make use of the skillset in some significant way.
The table that follows organizes all of this information in a more straightforward manner (with some additions of mine).
Table 1: Skillsets and tools covered by this course along with links to related SILS courses
|Skillset||Tools||Other SILS Courses|
|1.||Troubleshooting||Browser inspector; forums / online discussion; man pages /
||INLS 382; INLS 582|
|2.||Networking||SSH; FTP; traceroute; nmap||INLS 382; INLS 582|
|3.||Version control||git; GitHub||INLS 560; INLS 572; INLS 573; INLS 672|
|4.||Critical thinking||Brains; discussion||INLS 151; INLS 200; INLS 318; INLS 382; INLS 582|
|5.||Data handling||MySQL; Bash; CSV/TSV||INLS 523; INLS 623; INLS 624; INLS 626; INLS 756; INLS 760|
|7.||Writing using markup languages||Pandoc; Markdown; HTML5; Liquid/YAML||INLS 572; INLS 573; INLS 672|
|8.||Using remote / terminal shell commands||Bash; sudo; other command line tools||INLS 572; INLS 382; INLS 573; INLS 582; INLS 672|
|9.||Scripting / automation||Bash; MySQL||INLS 560; INLS 572; INLS 573; INLS 672|
|10.||Development -> production workflows||Jekyll; CodeAnywhere; GitHub||INLS 523; INLS 560; INLS 572; INLS 573; INLS 623; INLS 624; INLS 626; INLS 672; INLS 718; INLS 756; INLS 760|
|11.||Software management||APT; Bash||INLS 523; INLS 560; INLS 572; INLS 573; INLS 623; INLS 624; INLS 626; INLS 672; INLS 718; INLS 756; INLS 760|
During the exam period
The exam period for this class is 11:30-14:00 on Monday, 31 July 2017. You are all required to attend the exam session. We will be viewing everyone's presentations with Q&A to follow.
This should not take the entire time alotted, but plan for at least an hour and half to be safe.