-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Piloting of software dev course #72
Comments
Link in the Quercus page points to Course 2 for Course 3, and Course 4 to Course 1? |
For Course 3.1 We should mention we don't need a separate Pico and relevant equipment for each setup. (Unless that is the intent) For Pico Board, I believe we should mention getting the version with the GPIO Headers. A mention to look at the pinout to decide where to plug in the devices. For the Pipette I think more info about how the wiring goes is needed. Especially as we are using a setup board. And maybe some safety notices? For the Motor, we are getting three colours of wire so I think we should say what they normally indicate, I genuinely believe some people don't know. For the fan, the diagram could do with some more clarification, in particular we are soldering separating the headers and solder them to the board and the wires to the headers. The fan wires do have corresponding connection points and its not just connect the four wires. |
For 3.2 Quiz |
Throughout course 3 I feel that there is a significant push for hands-on experience and learning as we go. However, I think that more theoretical explanation of what we are doing would be nice. I feel like its buy this, read this, do this demo. Missing some why we are doing this and how it works, what benefits this approach has, possible use cases for this, etc. |
Not saying it should stay the same, but some additional context:
In short, while both can provide auto complete, my understanding is that pylance has distinct features from copilot. It seems Pylance is actually installed by default with the Python extension apparently. I think there's some setting where you get to adjust what (if any) framework to perform auto completion. https://marketplace.visualstudio.com/items?itemName=ms-python.python |
The knowledge check for the orientation modules has no place, even in Course 1 it is not listed on the course site. Potential to add it in to the course site. Can only be accessed through Quercus right now. |
For orientation courses, if this is not the first course they have taken they may not be shown the student identifier (or get to choose one again). We could mention that in this case, the identifier will be the same as the other courses. |
These are fixed. |
These should be distinct between courses now, though people are welcome to choose the same identifier if it's available. If it's not unique between courses, then the links probably need to be updated. @SissiFeng could you check to make sure that the gh classroom links match the readthedocs links for the orientation modules? (intro to git and github, intro to github classroom, and python refresher links). @linx5o if you think it's worthwhile, could you suggest some language in a separate PR (or here) to clarify? |
EDIT: looks like I had this warning in course 2, but left it out in courses 3 and 4 somehow. I'm adding the same warning as shown in https://ac-microcourses.readthedocs.io/en/latest/courses/data-science/2.0-orientation.html#getting-started to 3 and 4. |
Usage of containers is currently part of 4.8, however I feel that having a whole section dedicated to the usage of containers is also justifiable. I think that they provide a lot of benefits that more people should learn to utilize in different situations. |
While it might not make sense to create a separate module at this stage, providing additional content related to containers is feasible. Do you have any specific ideas about examples that could be used to show the benefits you mentioned? To be fair, I probably don't use containers as much as I should. One of the main places I started using them for is the course codespaces themselves, and this has been great for ensuring every user at least has the option to have a consistent environment. |
I think having all the courses in containers would make for easier maintenance of requirements. However, this does create more work, and would require students to under how to run files in the container. I find that it is useful when developing from different devices. |
Great points. As a note, whenever one of the GitHub classroom assignments is accepted, and then a corresponding codespace is created by the user, it uses a devcontainer file I or someone else wrote, usually identical to or somewhat modified from these files: https://github.com/AC-Classroom/intro-github-classroom/tree/main/.devcontainer To your point, this has ensured that when someone runs an assignment on codespaces, the environment is identical to that of other learners, which makes debugging a lot easier from a maintainer standpoint. |
The 4.4/4.6/4.7 assignments were revised. |
@RubainaFarin31, any updates? |
I think structure wise of the course so far, maybe have the assignment at the top? It's a bit confusing at the beginning that you can't access the assignment till the end when you have to self-report. Also just in general, I think it'd be nice to clarify whether the reading is for supplementary knowledge or practical steps to follow. 3.1 Comments: It’s a bit unclear whether the DigitalPipette class has units explicitly defined (e.g., μL) - may have misunderstood? 3.4 - Under Demo, "Learn about controlling robots with ROS ROS Navigation Stack" - is it supposed to say ROS twice? 3.5 - no major comments, pretty clear! |
Also, to clarify, the piloting of the course includes completing and submitting the quizzes and assignments. |
Once the tutorials and other content are complete and merged (should be within a day or two), then it would be great if you could start working through the content as a pilot student, providing feedback via GitHub issues, discussions, and occasionally PRs for @SissiFeng to look over.
The text was updated successfully, but these errors were encountered: