Skip to content
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

Feedback and Issues of Studies for JVK 2023 #162

Open
11 tasks
becknik opened this issue Oct 6, 2023 · 0 comments
Open
11 tasks

Feedback and Issues of Studies for JVK 2023 #162

becknik opened this issue Oct 6, 2023 · 0 comments

Comments

@becknik
Copy link
Contributor

becknik commented Oct 6, 2023

This is a list of all open issues and feedback I got by studies during working through the exercise sheets in 2023.

  • There was a case where a student was confused by the constructor of the Game class being overloaded to take only a verifier and one string for the window title without the actual game task.
  • A student got confused by the Sheet 2 Ex 1 c) with where to type in the commands and what the therm means
  • There were multiple questions about what to do on the second sheets ex 2 c) iii)
  • Sheet 3 Ex 2 has two d) Verifier objects in the gui, where one in meant for the part exercise e)
  • Neo's dropCoin method's JavaDoc says that Neo's broken when he has not coins left (he should be broke)
  • Neo's classes todo commentary specifies the wrong sheet and exercise, it should be sheet 2 ex 2 instead
  • sheet 3 ex 6 d): Many students missed the hint to just copy the code on the sheet and had trouble overwriting the collectCoin method. Those who just tried something on their own missed the super keyword and caused a infinite recursion
  • "Vererbung" instead of "Verebung" in the heading of sheet 3
  • When placing a wall manually in the UI Neo seems to not recognize it correctly
  • Sheet 1 Ex 3: No separate verifier exist for the last two part exercises
  • eclipse seems to be stupid trash ide which we should definitely stop to use. Spent uncomfy 30 minutes+ figuring out why Neo isn't initialized because the student just ticked the "Always launch without asking" checkbox on the "Errors exist in required project(s): FIUS-JVK - Proceed with launch?" pop-up in Eclipse. The code was just looking right & so I had to ask her to send me her project vai mail to notice the errors instantly in IntelliJ (fun fact: gmail doens't allow sending zip attachment). The scaling was so broken on the laptop. Why does this checkbox even exist?
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant