(sketch) looking for prior knowledge

Fine you want something to work. Here. Iāll copy paste. Iāll pattern match all the way down. Iāllā¦Hereās something that works. But I donāt know why it works. How about now? You want it to look nice? Hereās some NLP generated CSS.1
Thereās a common practice to just throw stuff at students and let them figure it out. But what does that mean? How can one figure it out? That āhowā should be taught explicitly: duckduckgo, blogs, stackoverflow, pair programming, code review, NLPs, etc. But these latter ones need, again, explicit instruction. I realize thereās so much to learn and teach that at the college level itās a fatalistic series of trade-offs. Still, the teacher has to be careful about cognitive overload and to whom theyāre teaching. What foundational skills, what prior knowledge, are you assuming? What about the students who donāt have them? Are they going to get punished? Or seen and recognized for their earnest work and progress?
When I write this Iām thinking about CS61B at Berkeley. I chose to go through it myself after my bootcamp to learn Java and data structures/algorithms. It was overload. I donāt see how students can get through this successfully without an abundant amount of knowledge and practice already.
That aside, what I really appreciated about the course is: it explicitly taught testing and debugging. Yes, I loved the conceptual narratives about data structuresāand the struggle to make my own implementations. I really do. I just need to repeat the courseāas my knowledge base, my prior knowledge, expandsāto actually grasp more of it.
Itās that background desire to have a broad conceptual understanding of computer science and programming concepts that distract me.
I find myself perusing further and further out because I end up reading more and more about a question. That web of connection is deep especially since Iām mostly browsing the inter-webs.
To supplement that and as a way to keep my work more focused, Iām reading technical books (ones at my level) and none technical books (ie. Stranger in a Strange Land, Life in Code, Number Sense) because Iāll filling in the gapsābecause these texts influenced how the pioneers worked and thought.
Itās why Iām listening to podcasts like Corecursive, watching Mike Conley's the Joy of Coding, and appropriately using Software Carpentry lessons. They are explicit. Paced. A wealth of prior knowledge that Iāve been searching for.
Posts with tag "sketch"
cover image Dalle generated.↩