First I take a look in Knuth, The Art of Programming.
Then I take a look in Cormen, Introduction to Algorithms.
If this doesn't answer my questions I'll hope timing some alternatives will, so I'd go for tests as soon as I have rough implementations ready.
It isn't certain that notes or UML cover or can predict the actual state of the program at some point or other during run-time (unless this is a formality, and then it is known to be formally so), so great debugging and inspection facilities are more important than extensive documentation of algorithms under development. When the code is stable documentation should explain it, though.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
First I take a look in Knuth, The Art of Programming.
Then I take a look in Cormen, Introduction to Algorithms.
If this doesn't answer my questions I'll hope timing some alternatives will, so I'd go for tests as soon as I have rough implementations ready.
It isn't certain that notes or UML cover or can predict the actual state of the program at some point or other during run-time (unless this is a formality, and then it is known to be formally so), so great debugging and inspection facilities are more important than extensive documentation of algorithms under development. When the code is stable documentation should explain it, though.