@koen_hufkens Exactly! It's not the code... it's understanding why/how.
AI6YR Ben's Post
In Reply To: this post
Likes: 0
Boosts: 0
Hashtags:
Mentions:
@koen_hufkens@mastodon.social
Comments
Displaying 0 of 1 comments
Koen Hufkens, PhD
In response to this post@ai6yr Some general observation in this context. For many students failure is hard.
Not that it is easy for anyone, but if you are never taught that this is part of the process it really bites.
In this context, teaching to the test (not doing open ended work) is doing a lot of students a great disservice.
If students ask me how I can figure out things I've never seen before I tell them I fail faster* and read manuals 😬
[* in my head]
@ai6yr Teaching failure, and the acceptance of it, and owning those mistakes is really important. First of all it keeps you humble, second it is key to a safety culture. And this bit is actually really important if you are dealing with people in wet labs, workshops, or real life. And, this makes the whole thing of "move fast and break things" utterly bonkers. Yes, failure is acceptable, if you don't intentionally create collateral damage. If you do, sit down and think long and hard. *sigh*
by Koen Hufkens, PhD ;
Mentions: @ai6yr@m.ai6yr.org @ai6yr@m.ai6yr.org @ai6yr@m.ai6yr.org @ai6yr@m.ai6yr.org
Likes: 0
Replies: 1
Boosts: 0