|
About
My Infrequently Updated Blog. The web-based journal of M. Forde, computer nerd, endurance athlete, and DeLorean owner
contact
Subscribe
Subscribe to a syndicated feed of my weblog,
brought to you by the wonders of RSS.
Flavors
There's more than one way to view this weblog; try these flavors on
for size.
index
circa 1993
Sections
main
musings
running
DeLorean
code
unix
album
TBM
Archives
2023
2022
2021
2020
2019
2018
2017
2016
2015
2014
2013
2012
2011
2010
2009
2008
2007
Disclaimers, Copyrights, Privacy, Etc.
ToS
Copyrights
Links
olix0r.net
netmeister.org
Giraffes
Eat. Run. Sleep.
|
|
|
Staten Island Half Marathon
Sunday was the Staten Island Half Marathon. I've been dealing with
overuse injuries as of late, my IT-band has been acting up and I
strained my right hamstring.
I wasn't sure if I'd be running or not, and the temperature was
predicted to be in the low- to mid-50's, so I wore my coldgear; I didn't
want to end up with hypothermia again if I was standing around for 2
hours in shorts.
It turned out that one of my teammates, Liz, wasn't sure if she'd be
able to finish. We decided to run together. And we did. We finished with
the exact same time of 2:34:00. I kept her from stopping and she kept me
from going to fast and re-injuring myself.
It took me an hour longer to finish the race than it normally would, but
I think it went quite well. My hamstring actually felt better after the
run. My IT-band was a little sore the next day, but it was better by
Tuesday.
Running at the slower pace, I was able to actually look around and enjoy
the scenery. The shores Staten Island were not as bad as I was
expecting. Over all, it was a good recovery run. A 13.1 mile recovery
run.
[/running]
[permanent link]
Bing!
It has come to my attention that searching bing for pictures of closed doors yields
pictures of my DeLorean.
[/dmc]
[permanent link]
Self Documenting Code
Despite what you think about your code, it is not self documenting. When
writing code add comments, describe what a function does, explain why
you're using that convoluted pointer arithmetic and bit shifting. I'm
sure it makes sense now, but someday you'll have to go back and look at
it and figure out what the hell you were doing. Or worse, I'll
have to go back and look at it and figure out what the hell you were
doing.
Sometimes it is important to have some sort of separate documentation
for the code; maybe some UML or ER diagrams, maybe some English text.
Use what ever it takes to explain what you were doing. Do not paste
snippets of your code into the text and call it documentation.That
is not documentation, that is code.
[/code]
[permanent link]
|
|