generated from mwc/lab_pipes
a4563a3576
the questions within the document. This lab felt different primarily because there weren't any visual elements like the drawing or turtle. I don't know if I was aware of this as I worked on this lab, but it reminded me a bit, after being prompted to think about the thinking, of function composition. At one point, I tried to see if I could make the input for the put command another terminal command, something like put (cat ...). It didn't work, though I have to admit not spending a lot of time looking into whether there was some syntax I was unfamiliar with that would've accomplished that. Similarly, I don't know whether I felt the way I was using the terminal was particularly different than the way we used the terminal in the last unit, like in the lab involving the ship. I think, having used the terminal briefly many years ago, being vaguely aware that the terminal is powerful, and being ignorant of exactly what the terminal can do, it all feels new but within the range of new experiences I was expecting, as much as anyone can expect the unknown. I didn't feel so much as stuck as a bit overwhelmed with the number of commands that were introduced at once. Once I read through the examples carefully, I knew which ones to refer to as I worked through the problems. I don't know that I "learned" them--that is, I don't know if they're committed to long term memory--but I feel like given a similar task and references materials I could perform well, assuming I performed well on this lab. |
||
|---|---|---|
| .commit_template | ||
| exercises.md | ||
| poetry.lock | ||
| pyproject.toml | ||
| words_1k.txt | ||
| words_10k.txt | ||
| words_100k.txt | ||
| words_370k.txt | ||