• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Bear Bibeault
  • Ron McLeod
  • Jeanne Boyarsky
  • Paul Clapham
Sheriffs:
  • Tim Cooke
  • Liutauras Vilda
  • Junilu Lacar
Saloon Keepers:
  • Tim Moores
  • Stephan van Hulst
  • Tim Holloway
  • fred rosenberger
  • salvin francis
Bartenders:
  • Piet Souris
  • Frits Walraven
  • Carey Brown

97 Things Every Programmer Should Know - Another question to the author

 
Greenhorn
Posts: 1
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
How long did it take you to write this book?
-Raul
 
Greenhorn
Posts: 22
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Its a collection of articles from several authors.
 
Ranch Hand
Posts: 10192
3
Mac PPC Eclipse IDE Ubuntu
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator

megan smith wrote:Its a collection of articles from several authors.



Then it should have taken so long as others are done with their articles.
 
megan smith
Greenhorn
Posts: 22
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
..Another questions why 97 why not 197 ? what is so special about this 97?
 
Marshal
Posts: 69900
278
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
When I worked in the lab, I often said "97 pieces", mainly because 97 was about the least likely number to be real, I thought.
 
Greenhorn
Posts: 3
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator

Campbell Ritchie wrote:When I worked in the lab, I often said "97 pieces", mainly because 97 was about the least likely number to be real, I thought.



Actually it follows an O'Reilly standard for tips books, like "97 Things Every Software Architect Should Know" and "97 Things Every Project Manager Should Know", at least that's my guess.
 
author
Posts: 44
  • Likes 1
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
The process of pulling the book together happened in two phases: an incubation phase and a public phase. I initially gathered contributions from a smaller group of contributors, so as to prime the contributions with the bar set at a good level. They were invited or contacted me having heard of the project by word of mouth. When the project went public, via Twitter, conference mentions, InfoQ, lists, etc., contributions came in from a far wider range.

The incubation phase took around 6 months, and was relatively slow burn, slow accumulation of articles that I edited as they came in. The public phase lasted about two months, and was shorter than originally planned because the participation was larger than expected. I managed to keep up with the editing, but it was certainly more intense! Once the cut-off date was reached there was relatively little editing work to do, so the challenge was to make the selection and address other book-related issues.
 
Greenhorn
Posts: 4
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator

megan smith wrote: ..Another questions why 97 why not 197 ? what is so special about this 97?



It's the largest two-digit prime.
I always thought that was obvious ...

 
Kevlin Henney
author
Posts: 44
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
See here for an answer to the question of "Why 97?"
 
There's a way to do it better - find it. -Edison. A better tiny ad:
Building a Better World in your Backyard by Paul Wheaton and Shawn Klassen-Koop
https://coderanch.com/wiki/718759/books/Building-World-Backyard-Paul-Wheaton
    Bookmark Topic Watch Topic
  • New Topic