Daily Productive Sharing 232 - A Book List by Jeff Atwood

One helpful tip per day:)

(The English version follows)

#reading

今天的书单来自 StackOverflow 的联合创始人 Jeff Atwood,这份书单包含了大量软件开发的经典图书:

  1. Code Complete 2
  2. The Mythical Man-Month
  3. Don't Make Me Think
  4. Rapid Development
  5. Peopleware
  6. The Design of Everyday Things
  7. About Face: The Essentials of Interaction Design
  8. The Inmates Are Running the Asylum
  9. Programming Pearls
  10. The Pragmatic Programmer: From Journeyman to Master
  11. Designing Web Usability
  12. The Visual Display of Quantitative Information
  13. Visual Explanations: Images and Quantities, Evidence and Narrative
  14. Envisioning Information
  15. Beautiful Evidence
  16. Regular Expressions Cookbook

Daily Productive Sharing 054 - 20201031 - A book list by Marc Andreessen
Daily Productive Sharing 060 - 20201107 - A book list by Patrick Collison
Daily Productive Sharing 094 - 20201224 - A book list for management
Daily Productive Sharing 157 - 20210323 - A book list for lockdown
Daily Productive Sharing 172 - 20210413 - A book list by Mergeflow
Daily Productive Sharing 174 - 20210415 A book list for finance
Daily Productive Sharing 180 - 20210423 - A book list for Suez Evergreen incident
Daily Productive Sharing 227 - 20210629 - A book list for software development by Gergely Orosz

如果你觉得今天分享有帮助,不妨把它分享给你的朋友

原链

Recommended Reading for Developers

需要更棒的简历,不妨试试我们的 CV Consultation

如果你也想成为更高效的人,欢迎加入我们的 TG group


Today's list comes from Jeff Atwood, co-founder of StackOverflow, and contains a wide range of classic books on software development.

  1. Code Complete 2
  2. The Mythical Man-Month
  3. Don't Make Me Think
  4. Rapid Development
  5. Peopleware
  6. The Design of Everyday Things
  7. About Face: The Essentials of Interaction Design
  8. The Inmates Are Running the Asylum
  9. Programming Pearls
  10. The Pragmatic Programmer: From Journeyman to Master
  11. Designing Web Usability
  12. The Visual Display of Quantitative Information
  13. Visual Explanations: Images and Quantities, Evidence and Narrative
  14. Envisioning Information
  15. Beautiful Evidence
  16. Regular Expressions Cookbook

Daily Productive Sharing 054 - 20201031 - A book list by Marc Andreessen
Daily Productive Sharing 060 - 20201107 - A book list by Patrick Collison
Daily Productive Sharing 094 - 20201224 - A book list for management
Daily Productive Sharing 157 - 20210323 - A book list for lockdown
Daily Productive Sharing 172 - 20210413 - A book list by Mergeflow
Daily Productive Sharing 174 - 20210415 A book list for finance
Daily Productive Sharing 180 - 20210423 - A book list for Suez Evergreen incident
Daily Productive Sharing 227 - 20210629 - A book list for software development by Gergely Orosz

If you find today's sharing helpful, why not share it with your friends?

Recommended Reading for Developers

Need a superb CV, please try our CV Consultation

Excerpt

To make better software, you need to understand how people work, and that is what the books I recommend tend to focus on.> In Code Complete, Steve notes that the average programmer reads less than one technical book per year.
I like this book so much that the title of this very website is derived from it – the examples of what not to do are tagged with the "Coding Horror" icon.
Rapid Development isn't about rapid development. It's about the reality of failure .
The unpleasant truth is that your team has to be very good to simply avoid failing, much less to succeed.
Our field is one of the few where change is the only constant, so it's only natural to embrace that change and try different "Rapid" development techniques.
At least have some idea of what works and what doesn't before you start– in McConnell's words, "read the instructions on the paint can before painting." Sure, it sounds obvious enough until you read this book and realize how rarely that actually happens in our field.
Designing software is difficult, to be sure, but designing a door is difficult too.
A lot of what we do is defensive: trying to anticipate what will go wrong before it does.
Sometimes great products fail for reasons beyond your control, no matter how hard you try.