cyborg-alchemist:snommelp: twitblr: These policies can help to improve the mental health of students
cyborg-alchemist:snommelp: twitblr: These policies can help to improve the mental health of students If the point is for the children to learn, then why wouldn’t you give them as many chances as it takes? What is the benefit of telling a child “you failed and that’s the end of it”? I’m 25, and in my trade school, our tests aren’t judgement, they’re testing to see what we’ve retained, and identify what we’re missing. If I weld a joint, and the CWI comes up behind me with a radiographic test for it and finds that I just laid hot metal on cold metal or it looks like a sponge inside, you know what’s gonna happen? You think they’re gonna give me a low score and tell me to move on? Fuck no. They’re gonna hand me a grinder and tell me to take it out and put it in right.When there’s actual work to be done, we don’t leave it at the first attempt if that attempt was shit. We don’t leave a trail of “what’s done is done.” If it takes you four attempts, that’s what it takes, and next time it’ll take fewer because you learned how to do it right after the third time. School, as it’s set up, with unforgiving deadlines and single attempt high stakes tests are building a shitty work ethic. It says “I tried once, and that’s all you’re getting.” It sets you up to leave a trail of cut losses and barely or unfinished projects as you scramble to get something, anything, turned in before the deadline.And we wonder now why nothing works at launch. This is not the point made above (which I think is really good!) But I have a theory that a lot of softwares don’t work at launch due to “agile project management.” Which I think was a…design philosophy(?) of sorts that came out in 2001. (I remember my dad learning about it and using some of the ideas pretty early on and how it suddenly became something you could be certified in instead of just…knowing it from launch)It’s not necessarily a BAD concept per se, and it has a lot of usefulness but also it can go very badly. basically it’s described as “an iterative approach to managing software development projects that focuses on continuous releases and incorporating customer feedback with every iteration.”…you know, like a good beta release! Present the software project to the client as you progress in designing it, maybe even have trial runs when it’s in an alpha or beta phase, and use their feedback to improve the design as you go! After initial release you’ll also get EVEN MORE feedback, because now the product is “complete,” so everyone getting it is using it and able to report any bugs, and you use that data to patch in any fixes, updates, etc. They have like, whole systems for learning this style of project management now and shit. But the tl;Dr is “instead of a big bang release of software (or waterfall project management) and kaboom now it’s done! You can do fancy MBA speak things like ’learn and adapt’ and ‘collaboratively work with the consumer.” And you do mini-releases or controlled beta releases or whatever else. That works great if you hire a company to design a software for a specific purpose and are actually collaborating with your designers. (Or it’s an internal thing between departments, or whatever). The problem is, some companies use agile philosophies but push off the “collaboration,” aspect to the end-user/intended customer and I can’t PROVE I’m right but I suspect this is why some software/website shit is often released blatantly incomplete, because ~*~agile~*~ management took over like, 21 years ago and some companies unfortunately push that concept onto the general public/their designers in the interest of the speedy release/crunch/efficiency part of Agile design but not the actual…end quality product part. …which, to bring it back to the point, iterative learning and production (when used correctly and effectively) is…a thing in real world adult jobs do literally all the time, and is a very good skill to learn. It’s good to know how fix mistakes, retry problems looking for new ways for information to “click,” identify improvements in approach or method, etc. This teacher is not stunting anyone they’re helping them learn a lot of skills. Lots of stuff in adult jobs also isn’t just “done wrong” or “done right.” Some of it is more like “is this done EFFECTIVELY?” Or “is the flow of how to do this task making sense for our needs and the people doing the task?” Or “if this is difficult for people, how do we make it easier/more approachable/more useful?” And “can we edit, rethink, redesign this?” And if you’re not allowed to fail and retry in school because learning becomes black and white, correct/incorrect on the first try only, then you can end up struggling with adapting to the hashtag real world where a lot of shit is way more grey and also you will always make mistakes and need to know how to fix them! -- source link
Tumblr Blog : twitblr.tumblr.com