Slashdot Mirror
Best Software Writing I
meryl (Meryl K. Evans) writes "Having been in process management in a software organization for over ten years, I've seen too many articles and books on the topic that worked better than Valium for putting me to sleep especially since they have no side effects. You know that Joel Spolsky is one of the best writers on the topic of software. However, in this book he stands aside and lets others demonstrate that he isn't the only one who can write about software in English and captivate you." Read on for Evans' review.
Best Software Writing I: Selected and Introduced by Joel Spolsky
author
Joel Spolsky, editor
pages
328
publisher
Apress
rating
8
reviewer
Meryl K. Evans
ISBN
1590595009
summary
29 essays by multiple authors covering a range of development-related topics.
Joel on Software fans won't be disappointed in the selection of authors as they deal with the concepts Spolsky writes about on his site. Some readers may be expecting a book solely on software development. Even Joel goes beyond this. Some folks might be disappointed that most of the articles, blog entries, speeches, and essays are available somewhere on the Web. I only recognize a few of the authors and their articles, though, so I would've never known about the others had I not found this book.
The essays cover a wide range of development-related topics. They include coding style, outsourcing programmers, dealing with Excel as a database (gag, gag), using social software (and the things that are right and wrong with these shared spaces), emerging digital rights, and defining the two-phase commit process a la Starbucks. A few of them are nothing but comics. The one on Windows search will knocks readers out of their chairs laughing, at least it did me.
The book also contains business-related essays that address a few problems affecting many companies -- namely team compensation and forced overtime which often spills over the weekend. Joel introduces every essay and includes notes clarifying abbreviations, names, or terms that you most likely know. But other people who would benefit from the book may not -- cut Joel some slack for providing these notes.
The manager benefits from the book because she gains insight into the developer's perspective, which could help her become a better leader. The developer benefits because many of the issues covered can affect him no matter what language he uses for development. If you belong to neither management nor development, the best way to decide if the book is for you or not is to review the table of contents and reviews. If you find only one or two interesting possibilities, search for them online instead.
I'm one of those who belong to neither group. My software organization background has been along the lines of an analyst and process manager. Even I find that most of the essays are enjoyable or educational. Only one or two lost me.
While most of the content is available on the Internet for free and all of you can find it, the book is worth the bucks. It's nice having a collection of high-quality writing related to software and the business in one place instead of trawling the Web for it. Furthermore, you get an opportunity to read offline -- if you manage to tear yourself away from the monitor every now and then at least; I read most of the book while traveling on an airplane. The flight flew by, thanks to the book. I appreciated and absorbed the essays better by reading them in the book than I would have had I read them online.
You can purchase Best Software Writing I from bn.com. Slashdot welcomes readers' book reviews -- to see your own review here, read the book review guidelines, then visit the submission page.
The essays cover a wide range of development-related topics. They include coding style, outsourcing programmers, dealing with Excel as a database (gag, gag), using social software (and the things that are right and wrong with these shared spaces), emerging digital rights, and defining the two-phase commit process a la Starbucks. A few of them are nothing but comics. The one on Windows search will knocks readers out of their chairs laughing, at least it did me.
The book also contains business-related essays that address a few problems affecting many companies -- namely team compensation and forced overtime which often spills over the weekend. Joel introduces every essay and includes notes clarifying abbreviations, names, or terms that you most likely know. But other people who would benefit from the book may not -- cut Joel some slack for providing these notes.
The manager benefits from the book because she gains insight into the developer's perspective, which could help her become a better leader. The developer benefits because many of the issues covered can affect him no matter what language he uses for development. If you belong to neither management nor development, the best way to decide if the book is for you or not is to review the table of contents and reviews. If you find only one or two interesting possibilities, search for them online instead.
I'm one of those who belong to neither group. My software organization background has been along the lines of an analyst and process manager. Even I find that most of the essays are enjoyable or educational. Only one or two lost me.
While most of the content is available on the Internet for free and all of you can find it, the book is worth the bucks. It's nice having a collection of high-quality writing related to software and the business in one place instead of trawling the Web for it. Furthermore, you get an opportunity to read offline -- if you manage to tear yourself away from the monitor every now and then at least; I read most of the book while traveling on an airplane. The flight flew by, thanks to the book. I appreciated and absorbed the essays better by reading them in the book than I would have had I read them online.
You can purchase Best Software Writing I from bn.com. Slashdot welcomes readers' book reviews -- to see your own review here, read the book review guidelines, then visit the submission page.
From the publishers of "Worstest Book Titling 3".
Links to the essays in Best Software Writing can be found here: http://brevity.org/misc/bestswi.html
Not everyone is a fan of Joel's. This reviewer obviously is. It would be interesting to get a more objective viewpoint.
---------------------------------------------
SERENITY NOW!!!!!!!!!!!!!!!!
When is the hindi translation of the book going to be available so that we can all enjoy it?
For the last time, Slashdot book reviewers, a summary is NOT a review!
As usual, the book is cheaper at amazon: http://www.amazon.com/exec/obidos/tg/detail/-/1590 595009/qid=1126809765/sr=8-1/ref=pd_bbs_1/002-2832 463-9709664?v=glance&s=books&n=507846
(Don't worry, no referrer id in the link, I'm not trying to get rich off of you)
Cool. I might consider getting it.
Referrer-free Link: http://www.amazon.com/exec/obidos/ASIN/1590595009/ 104-8120704-9951931
Even $17 seems like a lot for something you can find for free on the internet.
my grammar book from my Freshman year of college. This is bad! I've become so desensitized to bad grammar that I didn't even notice the error in the title.
Evil people don't think they're evil. - George Lucas, Making of Ep III
Modern conservativism is a proven failure. Ideology is almost always a destructive force in governance. The best government is dedicated to liberty, justice, and democracy, with science being the thread that ties each together.
Hmmm, you do realize that this is very idealistic. Liberty and justice, for example, are often at struggle with each other. A government can only give justice to one at the expense of the liberty of another. Sprinkle a little reality in there and you're on the right track.
I had read a good portion of it before, but some of the stuff is always good to reread. And, on occasion, if someone is standing in my cube and we happen to be talking about forced overtime... (ugh)... then it's a lot easier to hand them the book, flip it to ea_spouse's article, then tell them that they should someday go and find it and maybe read it once they find it.
Then write one.
See my journal for slashdot ID's by year. Mine created in 2005. http://slashdot.org/journal/289875/slashdot-ids-by-year
Do you think advertising for amazon for free (as they dont have to pay the normal referer, thus increasing their profits) will give you a moral highground?
I rather give (the provision part of) the money to somebody who searched out the link than to multibillion corporation.
HI O WISE PRINCE. WHT TOOK U SO DAM LONG?
You do realize that Joel didn't write any of these essays, right?
That's why I get a receipt, it's like a session token saying that I am owed packet 123 (drink) for having sent request ABC (cash + order).
---Throwing the golden wrench of reason into the complex machinery of life since 1979.---
stuff |
Good lord! Is writing on the topic of software really that bad?
Oh wait, that's your opinion. ...and oh wait, this is Slashdot.
...just my 2 gil.
I have read this book as well, and I thoroughly enjoyed it. I'm still a college student in CS and found most of it informative and interesting. It was not without its low points, however. A good read, IMHO. 95% non-bullshit.
just my two cents
Hey lay off! His .sig is the best!
Damn dude, if you get that wound up about a book, I'd hate to see what happens when you get a letter from the IRS regarding the $20,000 you claimed as a charitable donation to a charity called "Tentacle Hentai."
Uh, thanks. This is my first time here in the scary world of b00ks (as opposed to books).
useless sig advice - Read Nabokov.
You know that Joel Spolsky is one of the best writers on the topic of software.
You must have mixed him up with Paul Graham - Spolsky is usually just loud and annoying. Well, at least he's better than Shirky...
"The one on Windows search will knocks readers out of their chairs laughing, at least it did me" I sure hope you used protection. It looks like you might have already caught grammatical SARS.
IT conversations have a recently recorded interview with Joel in which he tells about the book. Great stuff.
IT Conversations's interview with Joel
-- A Mathematician is a machine for turning coffee into theorems. - Paul Erdös
I enjoyed reading his earlier book "Joel On Software", but I think you will learn far more from...
"Analysis Patterns" by Martin Fowler
"Patterns of Enterprise Application Architecture" by Martin Fowler.
"Design patterns : elements of reusable object-oriented software" by Eric Gama et al
And for database stuff I would recommend
"Agile Database Techniques" by Scott W. Ambler
Yeah, but books and articles about programming won't bring you down nicely from a three-day coke binge. Believe me, I've tried...
OFMG YOU AER SO RITE!!1 MICRO$HAFT SUX AZZ!
Dickhead.
Save yourself more than THREE BUCKS by buying the book here: Best Software Writing I. And if you use the "secret" A9.com discount, you can save an extra 1.57%!
Ever heard of a title called Code Complete written by Steve McConnell and published by Microsoft Press? Probably one of the top 5 "how to" software guides out there.
It's more about the author than the publisher.
The worst thing about the book is that Joel doesn't know when to shut up. Say Bruce Eckel writes an essay about how great Python is, and Joel doesn't like Python. So he prefaces the essay with his own comments about why you shouldn't use Python.
Hey Joel! Shut up and let the author's essay stand on its own already.
I heard Joel spolsky talk about this book on itconversations.com
The first thing I had to ask myself is:
Why doesn't somebody just list the URL's of all the articles somewhere so I can download everything?
If any of you know these essays, how about url's?
Robert Nagle, Idiotprogrammer, Houston
Don't you know that Tentacle Hentai is a 501(c)3 non-profit organization?
Game... blouses.
Better books to learn from are:
Development:
Executable UML by Mellor and Balcer and
Executable UML:How To Build Class Models by Leon Starr
The older Shlaer-Mellor books are valuable as well.
Software Requirements by Wiegers
Management:
Peopleware by DeMarco and Lister
Slack by DeMarco
Data:
An Introduction to Database Systems by Date
Wonderful post....but one must applaud M$ for making so many billions off of what once automatically accompanied all software - actual documentation.
Yet another post from kaleidojewel, trying to get a few nickels by filling up the Book Review threads with his referral-link-laden "Buy the book from MEEEEEEE!" pleas. Truly and predictably pathetic.
This isn't a bad thing, we can use the corpses to power our cars.
What is wrong with thousands of dead kittens?
y .catfuel.reut/index.html
They're worthless now that you can't make gasoline out of them anymore... http://www.cnn.com/2005/WORLD/europe/09/14/german
Go read "Code Complete" and tell me your attitude hasn't changed.
Here's a review I wrote of this book for The Perl Review, issue 2.0:
There's a lot of good writing in the world. Some of that has to do with software. So hey, why not put some of it in a book?
Therein lies the apparent purpose of The Best Software Writing I, brought to us by software bloggerexpertpundit Joel Spolsky. Beyond that broad categorical relationship, it's hard to see how everything in the book relates, either to each other, or to the reader.
I like tables, but I don't buy a book with various articles written about tables. If I want to build a table, I buy a book on building tables. If I want to look at antique tables, I'll buy a book about antique tables. I won't buy a book about tables and hope it has something I am interested in.
I don't want to say this is a bad book, because that might imply the content is bad, and hardly any of it is. Some of it to me is quite boring--which highlights my main problem with the book--but most of it is quite good.
The opening chapter by Ken Arnold on why languages should enforce strict whitespace use at the compiler level was useless. And the final chapter, by "why the lucky stiff," which attempts to teach Ruby with a few short guidelines and cartoon foxes, had me skimming the pictures before gratefully reaching the conclusion.
But in between there was some really good stuff, including Paul Graham's OSCON 2004 keynote address about what makes a great hacker, Raymond Chen's piece on why Windows retains backward compatibility for broken apps, and danah boyd's article about social software. There's an insightful piece by Clay Shirky about how to encourage good discussion and discourage bad discussion online, a perceptive article by John Gruber about how the browser's location field is the new command line, and an amusing PowerPoint presentation outline by Aaron Swartz about why you shouldn't use PowerPoint.
And you know they are good, because each piece has an introduction by Spolsky, telling you not just how good they are, but that Spolsky thought of it first. Some of the articles even refer back to Spolsky, which is nice, in case you forgot how great he is. Not that other people don't engage in similar practices: the last three pieces I mentioned above are related to me, in that Shirky favorably mentions Slashdot (where I work), and Gruber and Swartz are my acquaintances, and that's a big part of why I singled them out for mention. It just seems to me that Spolsky shines the light far too much on himself, to make the book almost as much about himself as the writing.
What's especially odd is that this book couldn't appeal to people who are not already into software, who don't already know who some of these people are, or who are familiar with the issues they are writing about. They won't get any of it. Yet the book is littered with footnotes from Spolsky explaining things like "iTunes" ("Apple's online music store") and "dev" ("Dev = developer = an actual computer programmer").
Which brings me back to the point of the book. It's not for non-software people, and it is not for software people, including those who enjoy this sort of thing so much that they already read it when it went online.
So what is the point? I don't know. Maybe it is just to make more of a name for Apress, by saying they published a book by known software bloggerexpertpundit Joel Spolsky.
...richie - It is a good day to code.
[Pruneau
I am not a fan of Joel's. I respect his writing. Who he is has no influence over my review of the book and he didn't write the book.
The geekygirl from Texas
Why
The manager benefits from the book because she
and
The developer benefits because many of the issues covered can affect him ??
Is that sexism?
Joel does make comments at the start of each article, some are inane to be sure - but the majority are pretty solid an interesting articles from a wide variety of people across the software industry. If you pay attention to Slashdot you'll probably have read a lot of them, but there were some I had not seen before that I found pretty thought provoking.
"There is more worth loving than we have strength to love." - Brian Jay Stanley
I figured him explaining some obvious stuff was so that you could hand a bookmarked section to a manager and not have them get too lost.
I agree it's a bit havy on the Joel aspects, but I really liked a lot of the articles (although I have a rebuttal for that whitespace guy, who I consider 100% utterly wrong).
"There is more worth loving than we have strength to love." - Brian Jay Stanley
"Not everyone is a fan of Joel's."
Nooo! it can't possibly be true. Every word of his is truth. Just ask Phil Greenspun, who disagreed with Joel's sideline advice to replace BSD/TCL/AOLserver with Windows NT, IIS, and C#... the company may have folded, their customers may have been lost, but let no-one say it was bad reasoning!
I used to recommend (well, I still do, actually) Writing Solid Code by Steve Maguire to programmers. (Nowadays I guess it's a bit C-centric, but the principles are the same, and I'd say if you have trouble grasping the code concepts in the book, you're not ever going to write solid code anyway.)
Some people had the typical "Ha! Microsoft! What can they tell me about writing solid code?!" attitude.
A while later they'd finish it, and usually derisively tell me they'd learned nothing from it.
Almost invariably with such people, I would later look at the code they produced and think, "You're right. You learned absolutely nothing from that book."
Ah well. Such is life.
EOM
Joel has already published 2 other books with Apress. His book on User Interface design wasn't half bad.
Ewige Blumenkraft.
Yes, I didn't mean to imply they hadn't, just that this was another one.
There's a somewhat less fawning review at http://www.larkware.com/BookReviews/best.html
Sigs? Sigs? We don't need no steenkin' sigs.
You dont have to be for this book. I dont think he has a single article in it.
Btw: there is an essay in there by Rory Blyth, if you dont think it is funny you have never worked in the real world. But the great thing is, the essay is a blog post. you can read it here.
http://neopoleon.com/blog/posts/434.aspx
Bad User. No biscuit!
I picked it up on a whim while shopping for managed DirectX books at borders the other day after picking it up (literally) and reading though a few of the essays. This one's full of not only good observations about software development, BUT also has several good articles about geeks in businesss, and how they interact with the dreaded non-technical management types.
This is worth the money just to pick up and have someone rationally present alterantive viewpoints. For instance, I would LOVE to have a company adopt the no-bonuses policy coupled with salary advancements and promotion as an alternative. In every company I have ever worked for, bonuses have caused huge amounts of turmoil and I agree with the premise that everyone would be happier (and more creative) without the kind of intellectual sword of damacles a late or missing promised bonus program can cause in an IT shop. I watched a Peoplesoft shop come very close to falling apart after management decided not to pay promised bonuses one year, and I think that while this is in every way a problem of management, I agree with the essay's author that fault or not the whole process becomes a huge demotivator in place of an intentioned boost.
Again, the above is just one example from one essay in this volume. Agree or disagree with the points of view contained in the book, but the act of thinking about the problems that are presented here are going to happen along the course of most projects anyway, and I like to take things head-on.
I understand most of the articles are available online, but I this is one technical book that is actually fireside readable (IMHO) so I picked up the dead tree edition.
Highly recommended to IT folk
-chitlenz
Imagination is the silver lining of Intelligence.
Comment removed based on user account deletion
I bought and read this book, I have been meaning to write up a full review, but never have the time, so here is a short jist. It was a waste. The few gems on social software design and humorous cartoons are the only redeming quality. Joel's intros are fine, but his choice in articles is pretty poor.
The worst part is that the only article that actually dealt with software development/design/writing is a 2 page jib at microsoft about their window search system interface. The rest is mostly filled with management info that has nothing to do with software writing. There were three or four articles on performance metrics for 'knowledge workers' that all said the same thing ("They suck"). There was one delusional article that talked about how only Python coders were real coders and all other coders are fake pansies. That same author talk about how to recruit "hackers" (ie: Python coders). His basic jist was to offer a work environment just like your mother's basement and the uber python coding hackers will beg you to let them work for you.
A better title would have been "Mangerial info and other crap from people loosely related to computers: Final Volume"
-Rick
"Most people in the U.S. wouldn't know they live in a tyrannical state if it walked up and grabbed their junk." - MyFirs
In Soviet Russia, Best Software Writing you!
A review of a software book my a "process manager"? Puh-lease. Go sharpen your head.