The deadline for submissions to be Ready for Editing is next Friday
(16th October). After that, new contributions will continue to be
taken for the site, but they won't be considered for inclusion in the
book.
If you have any editing work pending, it would be helpful if you could
address this over the next week. This applies both to items listed in
http://programmer.97things.oreilly.com/wiki/index.php/Contributions_in_Progress#Edits_Pending
And a few of the items in
http://programmer.97things.oreilly.com/wiki/index.php/Edited_Contributions
For which I have already contacted the authors.
All contributors should make a final check of their contributions. See
if there are any tweaks you wish to make, check the talk pages of your
articles for any relevant comments (where comments have referred to
phrasing, I have fixed relevant grammar issues, so don't worry about
those) and ensure that your bio is complete and up to date. One hint
for your bio: if you have a URL, make sure it is spelled out -- having
a "link to my blog _here_" doesn't work very well on the printed page
:^)
If you have items that are already in
http://programmer.97things.oreilly.com/wiki/index.php/Contributions_in_Progress#Ready_for_Editing
Don't worry, I will be reviewing these and contacting you over the
next couple of weeks. The deadline of 16th October is not a
constraint, although timely response will be.
If you have anything in
Then it needs to be wrapped up in the next week.
If you have any questions about the process please feel free to ask on
this list or to email me directly. If you want to discuss the state of
your contributions, please contact me directly.
Thanks,
Kevlin
--
________________________
Kevlin Henney
+44 7801 073 508
http://curbralan.com
http://kevlin.tel
________________________
Measure don't guess is now up and awaiting editing. Going to be touch to
pair this down to 97 ;-)
Regards,
Kirk
> Measure don't guess is now up and awaiting editing.
Thanks.
> Going to be touch to pair this down to 97 ;-)
Don't I know it!
Hi Kirk. I like this!
It reminds me of the day decades ago when my boss gifted me and all my
team with stopwatches: he was happy that our code wasn't ugly, but was
not happy with its user response time. (The ugly problem turned out
to be the way our "clean, O-O code" interacted with the compiler,
linker, and virtual memory manager, and the ugly fix turned out to be
arranging the source according to its order of use at runtime rather
than by class hierarchy.)
It's never too soon to start measuring, but it might be too late...