Tuesday, March 25, 2008

now the draft has gone extreme.

EDIT (26 march 08: 16:40): epilogue follows.

i think i've created a monster.

in my efforts to fill in the gaps in all my proofs, the thesis is starting to sound .. robotic. If my theorems were sub-routines and my thesis were program code, then my proofs would read like a series of procedure calls.

\begin{proof}
By Lemma \ref{metricspacecase} we see that ____ ...
As a result, from equation \eqref{lipweakconv} we obtain _____ ..
and hence, by Corollary \ref{specialcasedimtwo} it follows that _____ ..

.. blah blah blah
yakity shmakity ..

ad nauseum
\end{proof}


Now the proofs don't seem simple or clear anymore, which they really are. They're simply obfuscated by having to remember what Corollary #.# and Lemma #.#.# and Theorem #.# are ..

argh. okay.

i need a break, and to look at this from an impatient eye which will see and seek clarity in these mathematics.


EPILOGUE. i think i overreacted. too much caffeine all at once and too many hours spent thinking dwelling on the same ideas: it led me to jump to conclusions.

so i guess the quasi-draft isn't so bad, but it still needs work and .. um, an introduction.

3 comments:

Anonymous said...

here's a recent
discussion of proof style.
your in the struggle.
v.

Anonymous said...

"yours" in the struggle.

janus said...

much appreciated!