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

Suggestions/comments #158

Open
tstokke opened this issue Dec 19, 2023 · 4 comments
Open

Suggestions/comments #158

tstokke opened this issue Dec 19, 2023 · 4 comments

Comments

@tstokke
Copy link

tstokke commented Dec 19, 2023

Moving my CS1 course to Runestone and I'm going through all the chapters (through chapter 4 so far). I noticed a couple of things that seem like they should be addressed. My apologies if this has been posted somewhere and I missed it, or if this should be somewhere else.

1.5 shows the HTML tags for bold around print, where I assume you want print in bold. It does the same with one other word in the same window.

In the Chapter 2 mixup questions, it didn't seem obvious that the code was supposed to be exactly what was done in the Parsons problems. I love the flow from solving the algorithm to having to actually type out the solution, but it wasn't obvious that was the expectation. But, a lot of simple things are not obvious to me, so I might be the problem. :-)

In the Chapter 2 mixup questions, Activity 18, the expected text in the code is not the same as the text in the Parsons problem - "minutes" was added to the expected text. I'm worried that might confuse some of the students.

In 4.7.3 Q-4 the expected answer is "exception". The way I read it "exceptions" would be the answer, or "an exception" would work. Just grammar issues, but it took me a while to figure out what it wanted. I actually had to peek at the source. I wonder if the regex could make the ending s optional?

Love what I'm seeing. If I come across anything else I'll update this (if I can), or add a new entry.

Tom

@barbarer
Copy link
Owner

barbarer commented Dec 19, 2023 via email

@tstokke
Copy link
Author

tstokke commented Dec 20, 2023 via email

@tstokke
Copy link
Author

tstokke commented Dec 21, 2023 via email

@barbarer
Copy link
Owner

barbarer commented Dec 21, 2023 via email

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

2 participants