Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
T
talks
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Iterations
Wiki
Requirements
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Locked files
Build
Pipelines
Jobs
Pipeline schedules
Test cases
Artifacts
Deploy
Releases
Model registry
Operate
Environments
Monitor
Incidents
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Code review analytics
Issue analytics
Insights
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
osak
talks
Commits
eedf7d74
Commit
eedf7d74
authored
6 years ago
by
Lennart Klebl
Browse files
Options
Downloads
Patches
Plain Diff
Rob Pike in beispieldok
parent
30134feb
Branches
Branches containing commit
No related tags found
No related merge requests found
Changes
1
Show whitespace changes
Inline
Side-by-side
Showing
1 changed file
workshops/latex/beispieldokument/zeta_8.tex
+20
-18
20 additions, 18 deletions
workshops/latex/beispieldokument/zeta_8.tex
with
20 additions
and
18 deletions
workshops/latex/beispieldokument/zeta_8.tex
+
20
−
18
View file @
eedf7d74
...
...
@@ -70,26 +70,28 @@ können als einen Grenzwert der Zetafunktion, $\riemann$.
\end{center}
\end{table}
\section*
{
Epilog
}
Dieser Teil soll
\textcolor
{
red
}{
nicht
}
im Inhaltsverzeichnis auftauchen, und
erhält damit auch keine Nummer.
\\
Außerdem:
\begin{itemize}
\item
Strukturierte Dokumente sind einfach mit
\LaTeX
.
\item
Makros machen einem das Leben leicht.
\item
Formeln -- und auch der ganze Rest -- sehen toll aus.
\item
Referenzen auf alles mögliche, also (Unter)
$^
n
$
abschnitte,
Gleichungen, Abbildungen, Tabellen,
\dots
{}
sind automatisch richtig.
\item
Eigentlich ist das alles gar nicht so schwierig.
\end{itemize}
\vfill
% Der Befehl vfill fügt einen vertikalen Abstand ein, der den übrigen Platz
% ausfüllt
\section*
{
Epilog -- Ein paar Programmiertipps von Rob Pike
}
Most programs are too complicated - that is, more complex than they need to be
to solve their problems efficiently. Why? Mostly it's because of bad design,
but I will skip that issue here because it's a big one. But programs are often
complicated at the microscopic level, and that is something I can address here.
\begin{enumerate}
\item
You can't tell where a program is going to spend its
time. Bottlenecks occur in surprising places, so don't try to second
guess and put in a speed hack until you've proven that's where the
bottleneck is.
\item
Measure. Don't tune for speed until you've measured, and even then don't
unless one part of the code overwhelms the rest.
\item
Fancy algorithms are slow when
$
n
$
is small, and
$
n
$
is usually small.
Fancy algorithms have big constants. Until you know that
$
n
$
is frequently
going to be big, don't get fancy. (Even if
$
n
$
does get big, use Rule 2
first.) For example, binary trees are always faster than splay trees for
workaday problems.
\item
Fancy algorithms are buggier than simple ones, and they're much harder to
implement. Use simple algorithms as well as simple data structures.
\end{enumerate}
\begin{center}
\includegraphics
[width=0.5\textwidth]
{
ctanlion.eps
}
\end{center}
\vfill
% die beiden Abstände werden gleichmäßig verteilt. Das Bild erscheint also in
% der Mitte.
\end{document}
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment