• 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
  • Paul Clapham
  • Jeanne Boyarsky
  • Junilu Lacar
  • Henry Wong
Sheriffs:
  • Ron McLeod
  • Devaka Cooray
  • Tim Cooke
Saloon Keepers:
  • Tim Moores
  • Stephan van Hulst
  • Frits Walraven
  • Tim Holloway
  • Carey Brown
Bartenders:
  • Piet Souris
  • salvin francis
  • fred rosenberger

"Cpders At Work" - Book structure

 
Bartender
Posts: 4107
72
Hibernate Fedora Chrome
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hello Peter,

1 - What makes you write this book, being a technical guy writing a non-technical book (of course involving technical people) ?

2 - What are the key areas the book addresses?, ( i.e: how each people approach their coding (in technical point of view or in general))

3 - Does the book address the experience/type of work done by the interviewees?

Thanks in advance,
 
author
Posts: 48
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator

Vijitha Kumara wrote:Hello Peter,

1 - What makes you write this book, being a technical guy writing a non-technical book (of course involving technical people) ?

2 - What are the key areas the book addresses?, ( i.e: how each people approach their coding (in technical point of view or in general))

3 - Does the book address the experience/type of work done by the interviewees?

Thanks in advance,



To take those in order:

1. I'm not just a technical guy. I'm actually a was-gonna-be-a journalist who got sidetracked into the software world. I think Apress asked me to do this book because I was technical enough to do good interviews with these folks but also knew something about interviewing and editing. (Though I realized late in working on the book that perhaps the best preparation I had for doing this book was my high-school years of wanting to be a musician: my incessant reading of interviews in magazines like Modern Drummer probably burned the form into my brain at some deep level.)

2. Mostly I tried to get folks to talk about how they learned to program, both when they were starting out and over the course of their career, how they actually work now, and what they think about the current state and near future of programming. I was also interested in how the conceived of programming--what other intellectual disciplines is it like--and how they thought it fit into the world--should everybody learn to program or will it always be a specialized craft.

3. Certainly I talked with all of them about their history so readers should be able to understand where they're coming from.
 
Well THAT's new! Comfort me, reliable tiny ad:
Devious Experiments for a Truly Passive Greenhouse!
https://www.kickstarter.com/projects/paulwheaton/greenhouse-1
    Bookmark Topic Watch Topic
  • New Topic