Peter Seibel interviews 16 of the most interesting computer programmers alive today in Coders at Work , offering a brand-new companion volume to Apress’s highly acclaimed best-seller Founders at Work by Jessica Livingston. As the words "at work" suggest, Peter Seibel focuses on how his... read more
“Every now and then I feel a temptation to design a programming language but then I just lie down until it goes away.”L Peter Deutsch
At the end of the day, ship the fucking thing! It's great to rewrite your code and make it cleaner and by the third time it'll actually be pretty. But that's not the point-you're not here to write code; you're here to ship products.Highlighted by 51 Kindle customers
'One way is to make it so simple that there are obviously no deficiencies and the other way is to make it so complicated that there are no obvious deficiencies.'Highlighted by 42 Kindle customers
Readability of code is now my first priority. It's more important than being fast, almost as important as being correct, but I think being readable is actually the most likely way of making it correct.Highlighted by 37 Kindle customers
I think one thing that's really important is to not be afraid of your ignorance. If you don't understand how something works, ask someone who does. A lot of people are skittish about that. And that doesn't help anybody. Not knowing something doesn't mean you're dumb-it just means you don't know it yet.Highlighted by 35 Kindle customers
You were asking earlier what should one do to become a better programmer? Spend 20 percent of your time learning stuff-because it's compounded.Highlighted by 33 Kindle customers
But the fundamental rule is, write the code that uses the API before you write the code that implements it.Highlighted by 30 Kindle customers
the cleaner and nicer the program, the faster it's going to run. And if it doesn't, it'll be easy to make it fast. As they say, it's easier to optimize correct code than to correct optimized code.Highlighted by 30 Kindle customers
The most depressing thing about life as a programmer, I think, is if you're faced with a chunk of code that either someone else wrote or, worse still, you wrote yourself but you no longer dare to modify. That's depressing.Highlighted by 27 Kindle customers
In practice, nothing works. There are all these beautiful abstractions that are backed by shit. The implementation of libraries that look like they could be beautiful are shit.Highlighted by 22 Kindle customers
Structure and Interpretation of Computer Programs, which a lot of people are afraid of because it's Lispy, but I think does a really good job of teaching programming without teaching a language.Highlighted by 19 Kindle customers
About the Author
Acknowledgements
Introduction
1. Jamie Zawinski
2. Brad Fitzpatrick
3. Douglas Crockford
4. Brendan Eich
5. Joshua Bloch
6. Joe Armstrong
7. Simone 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
Appendix A: Bibliography
Index
We’re hiding the errata, movie connections, books that influenced this book, books influenced by this book, books that cite this book and books cited by this book sections. If you would like to add content to them, you must first make them visible.