<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Teaching on Christo Wilson</title><link>https://cbw.sh/teaching/</link><description>Recent content in Teaching on Christo Wilson</description><generator>Hugo</generator><language>en-us</language><copyright>Christo Wilson</copyright><atom:link href="https://cbw.sh/teaching/index.xml" rel="self" type="application/rss+xml"/><item><title>After-hours Command Line Basics</title><link>https://cbw.sh/teaching/linuxbasics/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://cbw.sh/teaching/linuxbasics/</guid><description>&lt;h2 id="general-information"&gt;General Information&lt;/h2&gt;&#10;&lt;table&gt;&#10;&#9;&lt;thead&gt;&#10;&#9;&#9;&#9;&lt;tr&gt;&#10;&#9;&#9;&#9;&#9;&#9;&lt;th&gt;&lt;/th&gt;&#10;&#9;&#9;&#9;&#9;&#9;&lt;th&gt;&lt;/th&gt;&#10;&#9;&#9;&#9;&lt;/tr&gt;&#10;&#9;&lt;/thead&gt;&#10;&#9;&lt;tbody&gt;&#10;&#9;&#9;&#9;&lt;tr&gt;&#10;&#9;&#9;&#9;&#9;&#9;&lt;td&gt;&lt;strong&gt;Instructors&lt;/strong&gt;&lt;/td&gt;&#10;&#9;&#9;&#9;&#9;&#9;&lt;td&gt;&lt;a href="mailto:petrauskas.m@husky.neu.edu"&gt;Martin Petrauskas&lt;/a&gt; and Christo Wilson&lt;/td&gt;&#10;&#9;&#9;&#9;&lt;/tr&gt;&#10;&#9;&#9;&#9;&lt;tr&gt;&#10;&#9;&#9;&#9;&#9;&#9;&lt;td&gt;&lt;strong&gt;Classroom&lt;/strong&gt;&lt;/td&gt;&#10;&#9;&#9;&#9;&#9;&#9;&lt;td&gt;Behrakis 010&lt;/td&gt;&#10;&#9;&#9;&#9;&lt;/tr&gt;&#10;&#9;&#9;&#9;&lt;tr&gt;&#10;&#9;&#9;&#9;&#9;&#9;&lt;td&gt;&lt;strong&gt;Time&lt;/strong&gt;&lt;/td&gt;&#10;&#9;&#9;&#9;&#9;&#9;&lt;td&gt;Mondays, 6-7pm&lt;/td&gt;&#10;&#9;&#9;&#9;&lt;/tr&gt;&#10;&#9;&lt;/tbody&gt;&#10;&lt;/table&gt;&#10;&lt;h2 id="why-command-lines"&gt;Why Command Lines?&lt;/h2&gt;&#10;&lt;p&gt;The command line was one of the first interfaces through which people could dynamically interact with computers. In the 70&amp;rsquo;s and early 80&amp;rsquo;s, it was essentially the &lt;em&gt;only&lt;/em&gt; way to interact with mainframe and proto-desktop computers. Even today, all operating systems support command line interfaces of some sort.&lt;/p&gt;&#10;&lt;p&gt;Given how sleek modern operating systems are (i.e. with mice, touch screens, and 3D-accelerated application windows), this begs the question: why do we still need command lines? The answer is that &lt;em&gt;command lines are powerful&lt;/em&gt;. For many tasks, they are faster and less error prone than alternative interfaces that rely on windows, mice, clicking, tapping, etc. Further, command lines are ideal for automation. It is trivially easy to automate and systematize repetitive tasks using a command line; tasks that would otherwise be monotonous and time consuming. Lastly, command lines are ideal for accessing and controlling computers remotely. In an age of cloud computing, the need to remotely administer resources is greater than ever. In summary: command lines are not a useless relic from computing history; they are a vital and powerful tool of the present.&lt;/p&gt;</description></item></channel></rss>