Video: Tinderbox Meetup 15 October 2022 on Vimeo
Chat log: meeting_saved_chat.txt.zip (1.7 KB)
I thought it very interesting, not least because—as part of solving a problem in real time—it tripped over a number of real world confusions relating to (‘each’) loops:
var variables have to be declared, why aren’t they for loops? Tech-trained readers: check your privilege here before replying. One person’s ‘obvious’ rule is an unguessable magic incantation to another. Disclaimer: I have a foot in both camps here.
where within a loop you do a thing does matter.
- loops where different things need to happen depending on the currently in-scope item. For example, collecting discrete lines of text into a single variable but saving that only when a new set of such data is detected.
These sort of things are, at best, only obvious after the fact.
We whizzed through the topic in the meet, but I sense the task would be useful to revisit in much slower time. Indeed, using some of the mis-steps, as recorded† are useful to show how intuition is often a false friend. Sawing off the branch upon which you are sitting might feel like the right thing to do, but still ends badly.
None of the above speaks ill of the contributions made. the mis-steps in the recording show the errors we all make in the moment. With more time/less rush, we might make fewer mistakes. But, our real aim is to make no mistakes.
†. Seeing mistake can be helpful. It’s useful to see those we think ‘know’ the answers mess up, as we all do. It doesn’t make the hill we have to climb less steep but it does make the possibility of our arrival at the summit more believable. We tend, for concision, to edit out the mis-steps, but I’m coming to see that in a learning scenario they are often more usefully left in: the ‘expert’ is only making the same mistake a learner will.