mirror of
https://github.com/janishutz/eth-summaries.git
synced 2026-03-14 17:00:05 +01:00
[NumCS] Finish householder and givens
This commit is contained in:
@@ -33,7 +33,6 @@
|
||||
\vspace{4cm}
|
||||
\begin{center}
|
||||
\begin{Large}
|
||||
\quote{Wer in Python Type annotation benötigt, der soll kein Python verwenden} (2025-10-09T10:43) % FIXME: Marked for removal
|
||||
\quote{Wenn ich keine Lust habe, das zu berechnen, dann wende ich einfach Gewalt an}
|
||||
\end{Large}
|
||||
|
||||
@@ -77,17 +76,6 @@ We have also taken some explanations and code examples from the slides of our TA
|
||||
\color{MidnightBlue}\fbox{\href{https://n.ethz.ch/~muellerni/courses/numcs25.php}{here}}\color{black}
|
||||
% TODO: Update this when n.ethz is taken offline completely
|
||||
|
||||
|
||||
To add to the one quote regarding Python and type annotation: This is objectively wrong and a really hot take.
|
||||
Yes, this applies for small projects, but libraries \textit{DO} need type annotation, as you can't possibly read the entire library's code to use it.
|
||||
The reason this quote was even included here is that his coding style is really awful (yes, there were semicolons in his Python-code sometimes)
|
||||
and he rambled about bad coding style for about 10 minutes in this lecture.
|
||||
|
||||
Meanwhile his code has variable names that neither future him, nor anybody else can make much sense of intuitively.
|
||||
You can get away without type annotation in Python, even in larger projects, but only if you give variables proper names!
|
||||
|
||||
Moral of the story: Use descriptive variable names and do NOT use $t$, $tt$, $ttt$, \dots
|
||||
|
||||
% ────────────────────────────────────────────────────────────────────
|
||||
|
||||
% ╭────────────────────────────────────────────────╮
|
||||
|
||||
Reference in New Issue
Block a user