chore: improve wording, grammar fixes

This commit is contained in:
2026-08-27 17:45:24 +02:00
parent f0ab4c0939
commit e49e2b4df9
12 changed files with 84 additions and 58 deletions
+8 -6
View File
@@ -4,17 +4,19 @@
Semester 3 is an interesting semester in terms of the courses, ranging from well taught (Analysis II and TI) to atrocious (NumCS).
The same applies also to Semester 4, but the courses there are easier for many people.
<small>I have a summary (or even script) available for all the courses in this semester, see [here](/summaries/semester3)</small>
## Numerical Methods for Computer Science (NumCS)
This is about as bad of a course as courses ever really get.
::: details The rant about the course {closed}
The course was entirely reworked for HS2025, where I took it, switching from C++ and Eiger to Python with NumPy and SciPy,
as well as changing the course structure and curriculum pretty significantly. The former of which really is an improvement,
as most data science happens in Python using NumPy. However, since the professor is from the Maths department teaching a CS course,
you can kinda see where this is going.
as most data science happens in Python using NumPy. However, since the professor is from the Maths department teaching a CS course, you can kinda see where this is going.
<small>He once had the brilliant idea to rant about "type annotation in Python bad" (i.e. one should *NOT* do it), which of course *generally* is BS.</small>
While the content is interesting, the poor teaching really made this course a chore.
Due to this, many people have stopped attending the lectures and simply went to the exercise classes, where TAs were working hard to explain the content in a more approachable way.
Due to this, many people have stopped attending the lectures and simply went to the exercise classes, where the TAs were working hard to explain the content in a more approachable way.
The weekly CodeExpert exercises also were a massive chore, with it not rarely taking longer to understand what the task was than implementing it,
due to the very poor way in which things were phrased. This is one of the few cases where using AI is absolutely essential, as it can save you so much time
@@ -41,10 +43,10 @@ Not much else is to be said other than do your practice for the exam and you sho
## Systems Programming and Computer Architecture (SPCA)
This course, while not *technically* bad is very underwhelming. The topic frankly is too broad for just a seven credits one semester course,
This course, while not *technically* bad, is very underwhelming. The topic frankly is too broad for just a seven credits one semester course,
which also doesn't help it much. Don't however be concerned that it would be very hard, it isn't.
Having a good understand of many of the concepts taught in DDCA certainly won't hurt in this course.
Having a good understanding of many of the concepts taught in DDCA certainly won't hurt in this course.
You will be learning to program in C, but not *really*. This is the primary problem with the course:
There is no incentive for you to do the exercises (which in fairness, are pretty cool to do), but so many great opportunities for making the course great were left on the table.
@@ -56,7 +58,7 @@ This you can do by solving old exams, or doing your own little project (or doing
## Theoretical Computer Science (TI)
By far the most unique course this semester, it is known for having a mid and endterm exam, which, if passed on average makes you pass the entire course.
Yes, you heard that right, if you pass these, you won't have to do the session exam!
Yes, you heard that right, if you pass these, you won't have to do the session exam! If you fail, then you still have the chance to pass the course by attending the session examination.
TI is a lot about learning to do certain kinds of proofs in a certain way.
You learn that automatically by solving the exercises that you need to hand in weekly.