pxt-microbit
pxt-microbit copied to clipboard
microsoft
The rest instruction has 2 different measurment units "on" or "in" it at the same time.
I'll explain my problem, because maybe there are better solutions to it then what I think of: The "rest" block, has "(ms)" writen on it, even when the parameter in it is of type Beat.Fraction. This is confusing to explain to students. (I know the "rest" function is overloaded and can therefor has an instance with integer as parameter, which is the number of ms to rest, but it is confusing, and I don't know how to explain to students why the 2 measurment co-exist on the block)
Other instructions (play tone for example) has the same over loading as far as I see, and does not have the (ms) writen in the block.
My suggestion is either remove the (ms) from the block. (Or having seperate blocks for the different types of parameters, which might cause the need for different blocks in other instructions as well) I have a feeling it can help teachers when teaching students to explore instructions and undertand all there aspects, not to bump into this kind of inconsistency.... Any solution where the measurment units of the parameter are clear - will be great! Thanks much!!!
@abchatra can you please help? There are more issues with the music blocks, and I'd love to discuss them and get a solution for teaching them, please....
@HanaZimmermanKarl thanks for the feedback. This block has been there for long time and changing them might break screenshots and tutorials at various points.
We have built a much simpler to use playSound block in beta site (arcade.makecode.com/beta). Would that solve the teaching issue? Feedback welcome here.
@abchatra Thank you very much for your quick reply!!
Went into the arcade.makecode.com/beta as you suggested.
Checked the rest block first.
It looks better because it does not have the (ms) on it:
But when reading the documentation of it, it is very confusing (Attached are 2 screen shots. showing that the rest instruction is shown with the beat fraction parameter in it, but in Python and Java script it shows the ms parameter, and then, when explaining the parameters, it is talking about number of milliseconds only)
Can the documentation refer to the issue?
Writing you an email as well...
Thank you Adhijith Chatra for your very quick response! I'd like to explain my needs a bit better:
I'm the head of a new project at the Israeli MOE (Ministry Of Education) that is called HighTechClass.
We are addressing critical thinking as well as collaboration, Creativity, Design thinking, Communication skills and more while teaching students to code. We are doing it for all. Not only for fast learners or interested learners. There is a huge difference between teaching (or guiding, through asking good questions) *all *students, and teaching those who are interested in learning to code. We are in a pilot year of teaching more than 17,000 8th graders throughout the country, in class, *by their teachers *(who were trained, but are not computer science teachers) to code and much more, through using makecode for microbit. Our pedagogical approach is based on guided discovery based learning. This means our lesson plans (that are used by all teachers that take part in this pilot, and will be used by all teachers next year) are full of questions and not answers or explanations. Students that are being exposed to coding through blocks, and are at the beginning of their journey, can not deduce the reason behind why (ms) is written on a block that gets a bit fraction type as a parameter, and it is even more confusing when reading the help....
Overcoming this, needs a lot of explanation, and not common sense deduction, which is, as I explained, something we try to avoid. It also adds some feelings of uncomfort to the students in their own ability to learn on their own. In the second half of the year we will use JavaScript, where addressing overload issues and other issues will make more sense, though, it is not my first choice to address those topics.
As far as I understand, the micro:bit is all about education. So if I understand correctly, these issues are of importance to the entire community that uses micro:bit.
Sorry for this very long email. This is to explain why it is an issue for me.
I've got more issues with the music blocks. I'll add them in the GitHub comments if you'd like, Or write them in another email. Which is best for you?
Having been a VP in a global edtech company, I know what you mean about the screenshots and tutorials. Maybe a MORE... section for the music category can be added, where other blocks (solving the issues I mentioned here) could be placed?
Again, thank you very much for your quick response, Hana
Abhijith Chatra < @.***>:
@HanaZimmermanKarl https://github.com/HanaZimmermanKarl thanks for the feedback. This block has been there for long time and changing them might break screenshots and tutorials at various points.
We have built a much simpler to use playSound block in beta site ( arcade.makecode.com/beta). Would that solve the teaching issue? Feedback welcome here.
[image: image] https://user-images.githubusercontent.com/6107272/192689762-7b8ac403-09e1-447f-8cd4-847df1f85d0f.png
— Reply to this email directly, view it on GitHub https://github.com/microsoft/pxt-microbit/issues/4843#issuecomment-1260383295, or unsubscribe https://github.com/notifications/unsubscribe-auth/A25SSFE4OQWYSNQ7CVHTEZLWAPEW5ANCNFSM6AAAAAAQF53774 . You are receiving this because you were mentioned.Message ID: @.***>
-- thanks!
Hana-Zimmerman-Karl 052-4339577
If it easier please send email to makecode at microsoft dot com. Happy to discuss with my team.
Hi @abchatra, Sent an email to [email protected], few days ago. Can you please confirm you got it? Thanks much!
Hi @abchatra again,
The name of the parameter as it apears in the help of the rest block (both in production and in the arcade new version), is ms.
It can be seen in the screenshots in previouse comments of this thread.
Naming parameters (as well as to variables and methods), is a huge issue when teaching programming.
Same goes with educating to decide on naming convention and stick to them in a team project.
Having a parameter named by the measurment units rather then by it's meaning to the user is not simple to explain, specialy when it is not the convention for all other measurment units in all instructions, as can be seen here:
Now that I'm addressing the JS part of the curriculum, it becomes a greater issue... Same goes with other music blocks that have the bit fraction parameter, and it is named ms in the help.
And it is an issue with the pause block as well.
If there is a chance to have a conversation about it, I'd appriciate it very much. Thank you for everything and thank you in advance, Hana
Hi @abchatra, Is there any update you can share with me? Any update will be greatly appriciated. I need to make decisions as to next year's curriculum, and your update will be of great help in that. Thank you very much.
@HanaZimmermanKarl I have marked it for the yearly summer release. We will look holistically at these API's by then. We don't typically do changes to the apis in the middle of the school year, just to keep things consistent for teachers.
@abchatra Thanks for the update. I guess this leaves me in the dark as to what changes if any are going to be added to your summer release. As I'm progressing with the curriculum, there are more pedagogical issues that need to be addressed. We are not using the music blocks at all in our curriculum because of major issues there, that I'd like to share. As I wrote, I'd still appreciate an opportunity to have a discussion. Thanks again for the update! Good luck!
Happy to discuss with you @HanaZimmermanKarl. Do you want to have a meeting?