The pragmatic programmer tips (opens in new tab)

(pragprog.com)

60 pointskunqiana15y ago9 comments

9 comments

If there's one thing in here that I wish I could drill into every programmer's head, it's that abstractions are longer-lived than details. So few programmers seem to understand how important abstractions are.

hga15y ago

According to the Antipatterns book, only 1 in 5 programmers "get" abstraction, which roughly matches my quarter century experience in the real world.

A corollary of this is that absent really good hiring practices, "democratic" design processes are doomed to fail, since the non-abstractionists invariably out vote the ones who get it.

dpritchett15y ago

This is a fascinating comment. As someone who thinks he gets abstraction I'd love to hear some real world examples on the off chance I'm deluded. How do we know if we're actually non-abstractionists?

2 more replies

GFischer15y ago

"Test Your Software, or Your Users Will Test ruthlessly. Don’t make your users find bugs for you." At my current workplace, this is seen as a feature, not a bug! (having the users find the bugs). And no, I don't work for Microsoft.

ledger12315y ago

I have not read this book but the list of tips seemed to be bit too much. I am really a fan of all simplicity and tips from getting real book.

But someone who has read both books can explain it better.

Sukotto15y ago

Well, for what it's worth, I really liked it and consider it a keeper. It's on my bookshelf between "Programming Pearls" and "Mythical Man month".

It's less about programming per se and more about how to think about programming.

silentbicycle15y ago

I found the book underwhelming, but then I realized that programming blogs have probably ripped off every single paragraph.

I preferred Kernighan and Pike's _The Practice of Programming_ to both TPP and Code Complete, though. _Programming Pearls_ (and its sequel) have also held up well to repeated reading.

j / k navigate · click thread line to collapse