Coders at Work: Reflections on the Craft of Programming and over one million other books are available for Amazon Kindle. Learn more


or
Sign in to turn on 1-Click ordering.
or
Amazon Prime Free Trial required. Sign up when you check out. Learn More
Sell Back Your Copy
For a $2.65 Gift Card
Trade in
More Buying Choices
Have one to sell? Sell yours here
Coders at Work: Reflections on the Craft of Programming
 
 
Start reading Coders at Work: Reflections on the Craft of Programming on your Kindle in under a minute.

Don't have a Kindle? Get your Kindle here, or download a FREE Kindle Reading App.

Coders at Work: Reflections on the Craft of Programming [Paperback]

Peter Seibel (Author)
4.2 out of 5 stars  See all reviews (56 customer reviews)

List Price: $29.99
Price: $18.25 & eligible for FREE Super Saver Shipping on orders over $25. Details
You Save: $11.74 (39%)
o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o
In Stock.
Ships from and sold by Amazon.com. Gift-wrap available.
Want it delivered Thursday, February 9? Choose One-Day Shipping at checkout. Details
Textbook Student FREE Two-Day Shipping for students on millions of items. Learn more

Formats

Amazon Price New from Used from
Kindle Edition $14.16  
Paperback $18.25  

Book Description

September 16, 2009 1430219483 978-1430219484 1

Patterned after the best selling Founders at Work, Coders at Work represents two years of interviews with some of the top programmers of our times. Readers will find out what their work habits are, coding preferences, language preferences, style choices and idiosyncrasies in the fascinating look at how some of the best in the world do their work.


Frequently Bought Together

Customers buy this book with Founders at Work: Stories of Startups' Early Days (Recipes: a Problem-Solution Ap) $15.38

Coders at Work: Reflections on the Craft of Programming + Founders at Work: Stories of Startups' Early Days (Recipes: a Problem-Solution Ap)


Editorial Reviews

About the Author

Peter Seibel is a serious developer of long standing. In the early days of the web, he hacked Perl for Mother Jones Magazine and Organic Online. He participated in the Java revolution as an early employee at WebLogic which, after its acquisition by BEA, became the cornerstone of the latter's rapid growth in the J2EE sphere. He has also taught Java programming at UC Berkeley Extension. He is the author of Practical Common LISP from Apress.


Product Details

  • Paperback: 632 pages
  • Publisher: Apress; 1 edition (September 16, 2009)
  • Language: English
  • ISBN-10: 1430219483
  • ISBN-13: 978-1430219484
  • Product Dimensions: 8.9 x 6.3 x 1.3 inches
  • Shipping Weight: 1.6 pounds (View shipping rates and policies)
  • Average Customer Review: 4.2 out of 5 stars  See all reviews (56 customer reviews)
  • Amazon Best Sellers Rank: #140,104 in Books (See Top 100 in Books)

More About the Author

Peter Seibel is either a writer turned programmer or programmer turned writer. After picking up an undergraduate degree in English and working briefly as a journalist, he was seduced by the web. In the early '90s he hacked Perl for Mother Jones magazine and Organic Online. He participated in the Java revolution as an early employee at WebLogic and later taught Java programming at UC Berkeley Extension. Peter is also one of the few second-generation Lisp programmers on the planet and was a childhood shareholder in Symbolics, Inc.

In 2003 he quit his job as the architect of a Java-based transactional messaging system to hack Lisp for a year. Instead he ended up spending two years writing a book, the Jolt Productivity Award winning Practical Common Lisp. His most recent book is Coders at Work, a collection of Q&A interviews with fifteen notable programmers and computer scientists.

When not writing books and programming computers Peter enjoys practicing tai chi. He live in Berkeley, California, with his wife Lily, daughters Amelia and Tabitha, and their dog Mahlanie.


 

Customer Reviews

56 Reviews
5 star:
 (33)
4 star:
 (14)
3 star:
 (2)
2 star:
 (3)
1 star:
 (4)
 
 
 
 
 
Average Customer Review
4.2 out of 5 stars (56 customer reviews)
 
 
 
 
Share your thoughts with other customers:
Most Helpful Customer Reviews

68 of 68 people found the following review helpful:
5.0 out of 5 stars Entertaining and Inspiring, September 16, 2009
By 
This review is from: Coders at Work: Reflections on the Craft of Programming (Paperback)
If you are a person who cares at all about the art, craft, or science of software development, you will not be able to put this book down.

Seibel (a hacker-turned-writer himself) talked to some big names in our field. Topics covered include: How do you learn to be a programmer? How do you perfect your skills? How important is formal education? Which programming languages are good and which are terrible? What kinds of tools do great programmers use? (Which text editors? IDEs? Debuggers?) How do you reason about a program, bottom-up or top-down? What's the best way to collaborate with other coders? etc. etc.

As you might expect, the interviewees agree in some areas and wildly disagree in others, but there are insights aplenty. Some answers may surprise you, like how many of these coders shun formal debuggers and use mostly print statements, or how many of them shun IDEs for Emacs (or even pen-and-paper).

Aside from the broad questions, Seibel gets the interviewees to open up about what it was like to work on the projects they are famous for. These stories are engaging and entertaining. Any coder who has stayed up till 4AM squashing bugs will find kindred spirits in these books. And the stories are somehow inspiring, as you realize that even great programmers suffer through the same frustrations and ups and downs that all of the rest of us go through.

Those interviewed also share insights into what they think of our modern world of programming. Most agree that we live in complicated and troubled times as we battle layer upon layer of software complexity. This book has lessons to be learned from the very brief history of our field, and advice for the future ("Keep it simple!").

This book is deliciously buzzword-free and the programmers interviewed give their honest (sometimes brutally honest) opinions about what they love and what they hate.

The author and all of those interviewed share a passion for programming and it's hard not to be swept up into it. Very good book.
Help other customers find the most helpful reviews 
Was this review helpful to you? Yes No


50 of 52 people found the following review helpful:
4.0 out of 5 stars By programmers, for programmers, September 18, 2009
By 
This review is from: Coders at Work: Reflections on the Craft of Programming (Paperback)
As a book, Coders at Work is in some ways not all that great. As a collection of the thoughts and opinions of a wide range of real programmers on what, how, and why they do what they do, it is a treasure.

I have to say that the first thing I noticed about the book was the cheap binding. The paper and print quality are not very good, I can't say I liked the basic typesetting or sans serif typeface very much, and I found quite a few typos despite not being a person who looks for (or generally finds) typos in published material. The small Related Titles ad on the back cover is a bit annoying as well - that sort of thing used to be tucked away in the front matter and restricted to a list of the author's other work. Ah well.

There is a short introduction describing the author's inspiration and a few themes he picked out after the interviews were completed, but not much else in the way of structure; the entire content of the book is the series of fifteen transcript style interviews, prefaced by short introductions. Many of the same questions are asked of each interviewee, which is nice for comparing their answers, but I got the impression that Seibel was pushing some people harder on certain issues: Ken Thompson on the wisdom of pointers for example, or Fran Allen on why it's really necessary to have more women in computer science, or Don Knuth on why it's important to pry open black boxes. It felt a bit like prefigured puzzlement in the face of programmers who hold on to ideas that go against what passes for conventional wisdom nowadays, and I would have preferred a more thoughtful and after the fact summary of what the author thought these less common ideas might have to contribute to the mainstream.

But analysis is not what this book is about, and that may be a good thing. As a programmer himself, the author is able to ask the questions that most programmers would probably ask without forcing the interviews to conform to a rigid agenda, and the result is six hundred pages of consistently fascinating material. What impressed me most was the sheer range of approaches and motivations on display: everything from Jamie Zawinski's largely unschooled route to a formidable level of skill and subsequent major contributions to influential projects, to to Peter Norvig's uncommon combination of practical hacker wizardry with an almost ethereally playful interest in a variety of higher level topics, to Fran Allen's old school appreciation of quality systems and frustration at the amount of regression and small-concept thinking in the current state of the art, to Dan Ingalls' desire to make his software as flexible and alive as possible. If you think you know what the programming world looks like, this book will show you that not even the giants really grasp the sheer diverse extent of it.

Interestingly, nearly everyone interviewed expressed dissatisfaction with the inflexibility, complexity, low quality, and sheer size of the modern software edifice, and those who had burnt out or who expressed interest in quitting programming were the youngest and closest to the mainstream. Sobering observation, or artifact of the interview selection process? Read and decide for yourself.

I'm a programmer who's read a lot of stuff about programming, including a lot of material by and about some the people in these interviews, and I could barely put the book down. If you're anything like me, you should get a lot out of this book.
Help other customers find the most helpful reviews 
Was this review helpful to you? Yes No


45 of 48 people found the following review helpful:
5.0 out of 5 stars Better than expected, September 16, 2009
By 
Luke John Crook (Los Angeles, California) - See all my reviews
(REAL NAME)   
This review is from: Coders at Work: Reflections on the Craft of Programming (Paperback)
Imagine a really good episode of "60 Minutes" dedicated to each programmer in this book. Well, this book is better.

The first questions asked of each interviewee serve to set the stage; "How did you get into programming". The detailed answers given allow the reader to relate to the interviewee as an individual. Did they fall into programming by accident as part of their existing job? Did they train to be a programmer? Did they start on a Lisp machine or an Atari 800?

From this initial introduction the author begins to dig deeper. These questions are not formulaic. The author does not rattle off the same 40 questions to each subject but has a deep understanding of the domain. Questions demand answers to problems or serve to highlight issues that the interviewee presents.

Ran into a problem? Was it a language problem? A design problem? A management or coworker problem? What issues lead up to the problem? Could anything have been done differently? Questions are asked on working conditions, languages, approaches to problem solving, influences from upper management, influences from other programmers, burn out, love for programming (do they still like it).

In the first interview in the book with Jamie Zawinski; we know his approach to software design, his approach to programming (top down/bottom up) his feelings on over-engineering, crunch-time, refactoring, how he knows when he is in over his head, his philosophy to coding in general "At the end of the day, ship the **** thing... You are not here to write code, you are here to ship products."

This is not a "Coders at work for Dummies". There is no appendix tallying up how many of the interviewee's prefer waterfall to agile, functional to imperative and there shouldn't be. Each interview requires thought and reflection from the reader.

I read until 3:30 am and then wrote this review. This is a good book.
Help other customers find the most helpful reviews 
Was this review helpful to you? Yes No

Share your thoughts with other customers: Create your own review
 
 
 
Most Recent Customer Reviews











Only search this product's reviews



Inside This Book (learn more)
Browse Sample Pages:
Front Cover | Table of Contents | First Pages | Index | Surprise Me!
Search Inside This Book:


Tags Customers Associate with This Product

 (What's this?)
Click on a tag to find related items, discussions, and people.
 

Your tags: Add your first tag
 

Customer Discussions

This product's forum
Discussion Replies Latest Post
Mistakes in Kindle Edition 0 Dec 1, 2010
See all discussions...  
Start a new discussion
Topic:
First post:
Prompts for sign-in
 


Active discussions in related forums
Search Customer Discussions
   
Related forums





Look for Similar Items by Category


Look for Similar Items by Subject