售价: ¥368.00 + 免配送费
亚马逊的其他卖家
加入购物车
¥370.90
此商品可以享受免费送货 详情
卖家: 亚马逊
前翻 后翻
正在播放... 已暂停   您正在聆听的 Audible 音频版本的样品。
了解更多信息
查看全部 3 张图片

Coders at Work: Reflections on the Craft of Programming (英语) 平装 – 2009年9月16日

平均4.3 星
5 星
49
4 星
19
3 星
4
2 星
4
1 星
4
平均4.3 星 80条美国亚马逊评论 us-flag |
| 天天低价·正品质优
|
分享

显示所有 格式和版本 隐藏其他格式和版本
亚马逊价格
全新品最低价 非全新品最低价
平装
"请重试"
¥368.00
¥368.00
全新品2 售价从 ¥368.00

click to open popover

无需Kindle设备,下载免费Kindle阅读软件,即可在您的手机、电脑及平板电脑上畅享阅读。

  • iPhone/iPad/Mac
  • Android手机或平板电脑

请输入您的手机号码,获取Kindle阅读软件的下载链接。



基本信息

  • 出版社: Apress; 1st ed. (2009年9月16日)
  • 平装: 632页
  • 语种: 英语
  • ISBN: 1430219483
  • 条形码: 9781430219484
  • 商品尺寸: 15.2 x 3.6 x 22.9 cm
  • 商品重量: 857 g
  • ASIN: 1430219483
  • 用户评分: 分享我的评价
  • 亚马逊热销商品排名: 图书商品里排第1,105,058名 (查看图书商品销售排行榜)
  •  您想告诉我们您发现了更低的价格?

商品描述

作者简介

Peter Seibel is a serious developer of long standing. In the early days of the Web, he hacked Perl for Mother Jones 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.

目录

  1. Jamie Zawinski
  2. Brad Fitzpatrick
  3. Douglas Crockford
  4. Brendan Eich
  5. Joshua Bloch
  6. Joe Armstrong
  7. Simon Peyton Jones
  8. Peter Norvig
  9. Guy Steele
  10. Dan Ingalls
  11. L Peter Deutsch
  12. Ken Thompson
  13. Fran Allen
  14. Bernie Cosell
  15. Donald Knuth


看过此商品后顾客买的其它商品?

商品评论

在亚马逊中国上尚未有买家评论。
5 星
4 星
3 星
2 星
1 星

此商品在美国亚马逊上最有用的商品评论 (beta)

美国亚马逊: 平均4.3 星 80 条评论
92/92 人认为此评论有用
平均5.0 星 Entertaining and Inspiring 2009年9月17日
评论者 Brian Carper - 已在美国亚马逊上发表
版本: 平装
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.
60/63 人认为此评论有用
平均5.0 星 Better than expected 2009年9月16日
评论者 Luke John Crook - 已在美国亚马逊上发表
版本: 平装
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.
66/70 人认为此评论有用
平均4.0 星 By programmers, for programmers 2009年9月19日
评论者 Timothy Jones - 已在美国亚马逊上发表
版本: 平装
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.
37/41 人认为此评论有用
平均3.0 星 Interesting if you're interested 2009年10月13日
评论者 D. Grady - 已在美国亚马逊上发表
版本: 平装 已确认购买
As advertised, this is nothing more or less than a book full of interviews with accomplished programmers and computer scientists, interviews conducted by someone who is also a thoughtful and experienced programmer. The downside of the book is that it has absolutely horrible design: the text is ugly, the paper is ugly, there are typos on almost every page, and that is really irritating. There is also nothing here to draw you in to the material if you aren't already interested, but if you're thinking about buying a book of conversations with computer programmers that's probably not an issue.

The upside is that the interviews are often really fascinating. Siebel does a good job; he has a set of stock questions that everyone gets asked, and seeing how different people respond to them is great, but he also does a good job of getting the interviewees talking about things they think are interesting and just letting them talk. Contrasting how different people tackle problems, listening to what these folks think are the big issues in programming today and seeing common threads; there's a lot of good stuff. It's worth reading. I'm giving it three stars because I don't think it's a book that will be worth reading a second time, and because it's so sloppily put together.
13/13 人认为此评论有用
平均5.0 星 Coders at Work: A Review 2009年9月16日
评论者 TheDarkTrumpet - 已在美国亚马逊上发表
版本: 平装
I wrote this originally on my web site, http:[...], but am reposting here as well:

About a year ago, I decided to ask a number of people what I should read, and what I should do to be a better programmer. Over the next year I spent a lot of time with these same people trying to learn how to be a better programmer. This book, Coders at Work, is one of those books which turns out to be one of the most helpful programmer-guides I've come across.

- Structure of the book:

At the start of each "chapter" (which is really an interview), there's a short description about who each individual is. From there the chapter continues with a basic "interview-style" format, where Peter asks a question, and the interviewee answers it. Usually there's a followup question to clarify the previous answer - which has both the positive and negative effects to say "Person A answered this way, person B answered this way" - so in other words, at times it's hard to say, for example, how Zanwinski's answer differed from Peyton's.

The first question asked is one very crucial for most people, though, which is more or less, "How did you get into this?"

- Topics Covered:

The topics covered is not specific to only coding - some of the topics include:

- How did one get into coding?
- What were some successful projects?
- What were some less-successful/failure projects and why?
- What type of education is useful (e.g. is a PhD useful?)
- What tools does one use and why?
- What does one enjoy about programming?
- How one works with others and the dynamic of that.

This book is *not* only about coding though! That's an important thing to recognize about this book - it's leaned a bit toward programmers in general, but these topics help to make a better programmer in general - not simply specific to just coding better.

Some of the topics discussed feels a little dated, with some technology that's being discussed well before I was born, but since many of these challenges exist as timeless and I see in my everyday life, they are still valuable to hear about.

- Likes:

The main thing I enjoyed about this book was the fact that it's extremely applicable to what I see each day. A perfect example was the very first chapter in talking with Zanwinski. In this chapter, he discusses the concept of "Worse is Better", and how the strive for perfection caused a company to fail. This very concept rings extremely clear to me, in I've seen a system that was developed in the "Worse is Better" philosophy, and the development of the current system has seen times where the "Right Way" caused huge delays in the development of the system. It was a breath of fresh air to hear someone else discuss a situation that was really close to one that I've been, and in some ways continue to be, in. This is the main thing that I feel I enjoyed about the book itself.

Another applicable thing I read was the reasons for getting a PhD - which I've been contemplating for well over a year now. To hear perspectives about the reasoning to get or avoid one helps a lot in the contemplation.

Along with that, the topics were very interesting - and many of the answers were very clear and to the point. One can tell that these words were exactly the way the person said it - and not edited. This is a great feature because it feels more like a dialog than just a story-telling session.

- Dislikes:

There are a few areas of the book that I feel could have been done a bit better.
- When describing more old technology (e.g. the computer that Peyton learned on), I felt I had no clue what this device looked like or anything. A quick google can help in a lot of these situations, but there's a certain disconnect from the book itself as one's reading. This can happen especially for younger developers who haven't heard of some of this technology.
- The rants on some of the languages (e.g. Perl) can be taken poorly by some. I found it kinda funny, and it's clear that it's the individual's opinion, but I can see some people being annoyed by that. There's not a lot that can be done about this besides cutting out content.
- Better identifying similar crucial questions that are asked to each individual would be helpful to hear the ideals that are different between each person. Those, with a special icon or something, would have been very helpful for comparing and contrasting differences.

- Summary:

Overall, I feel this book is quite good, a definite 4.5/5 stars. This book gives a "mentor feeling", when I honestly don't have a mentor at this point at my job. I found that many of the questions in this book provided insights into the difficulties I'm currently presented with, and offers suggestions on how to approach them. While this book will likely not be the totally definitive guide for all programming-related knowledge, it's definitely something I feel fits in a niche that currently isn't occupied by other books. I feel this will benefit all levels of programmers.

用户论坛