Jeff Atwood
Programmer and writer; co-founder of Stack Overflow and Discourse, and author of the Coding Horror blog, which he has written since 2004.
Jeff Atwood did not write this page. What is this?
It collects the places they publish and what they have said there, each linked to the source. They have no account here. Is this you? Claim it, correct it, or ask us to remove it from ppll.
Where they publish
Recommends rcmnd
What they recommendrcmnd 12 things — each backed by an exact quote.
Compiled by rcmnd.app, not by them: the quotes are theirs, and each links to the post it was copied from.
Recent
Regular Expressions Cookbook Recommends
I may be a card carrying member of the "Keep It Simple Stupid" club, but I'm making a meteor sized exception for regular expressions. Written properly, they will save you a tremendous amount of time in string manipulation, and I've never run across a project where they didn't come in handy somewhere.
blog.codinghorror.com 2004-02-02
The Visual Display of Quantitative Information Recommends
You don't need to own all four books in the series unless you're a completist (or a masochist, I suppose), but the first two are essential.
blog.codinghorror.com 2004-02-02
What others say about The Visual Display of Quantitative Information →
The Pragmatic Programmer: From Journeyman to Master Recommends
This book reminds me a lot of Programming Pearls, but it's actually better, because it's less focused on code. Instead of worrying about code, the authors boiled down all the practical approaches that they've found to work in the real world into this one book.
blog.codinghorror.com 2004-02-02
What others say about The Pragmatic Programmer: From Journeyman to Master →
Show 9 more
Programming Pearls Recommends
Programming Pearls is the next best thing to working side by side with a master programmer for a year or so. It is the collective wisdom of many journeyman coders distilled into succinct, digestible columns.
blog.codinghorror.com 2004-02-02
The Inmates Are Running the Asylum Recommends
This is the book that introduced the world to the concept of personas: rather than thinking of users as an abstract, difficult-to-describe, amorphous group of people, personas instruct us to talk about specific users who have names, personalities, needs, and goals.
blog.codinghorror.com 2004-02-02
About Face: The Essentials of Interaction Design Loved
It's a fantastically useful book; I've used whole chapters as guides for projects I worked on.
blog.codinghorror.com 2004-02-02
What others say about About Face: The Essentials of Interaction Design →
The Design of Everyday Things Recommends
Designing software is difficult, to be sure, but designing a door is difficult too. The nuances of design extend into every object you touch, whether it's some hot new SQL engine, or a humble shoe.
blog.codinghorror.com 2004-02-02
Peopleware Recommends
If you have any legitimate aspirations to be a "Team Leader" in practice instead of in name only, you need to pick up a copy of this book.
blog.codinghorror.com 2004-02-02
Rapid Development Recommends
Rapid Development isn't about rapid development. It's about the reality of failure. The vast majority of software development projects will fail: they will overrun their schedules, produce substandard results, or sometimes not even finish at all.
blog.codinghorror.com 2004-02-02
Don't Make Me Think Loved
The single best book on usability I've ever read. The title says "web usability" but don't be fooled by its faux specificity. Steve Krug covers every important usability concept in this book, and covers it well.
blog.codinghorror.com 2004-02-02
The Mythical Man-Month Recommends
I challenge any developer to pick up a copy of The Mythical Man Month and not find this tale of a long-defunct OS, and the long-defunct team that developed it, startlingly relevant.
blog.codinghorror.com 2004-02-02
Code Complete 2 Recommends
Steve McConnell's Code Complete 2 is the Joy of Cooking for software developers. Reading it means that you enjoy your work, you're serious about what you do, and you want to keep improving.
blog.codinghorror.com 2004-02-02