4 ms·
I will not pass final judgement on the book until I've had an opportunity to read it, of course. But my initial reaction to this title is one word: “Poorly.”
by shadowfiend 14y ago
I will not pass final judgement on the book until I've had an opportunity to read it, of course. But my initial reaction to this title is one word:
“Poorly.”
Not that there's anything wrong with that. Every application I've seen that was written in three days with any amount of functionality was also written poorly. But it didn't matter. Because you don't consume the application's code, you consume the application. The trouble with writing a book is that you do consume the product of the book directly. That's why I'm skeptical.
That said, maybe this book is awesome. That would be awesome, and hopefully would get more people riding the writing train and flexing that language muscle so many often forget about.
- StavrosK 14y ago"Everybody does have a book in them, but in most cases that's where it should stay." ― Christopher Hitchens
- pestaa 14y agoLooking forward to write both a technical and a non-technical book in the future, that quote is really hard to digest.
- StavrosK 14y agoIf you work hard enough on becoming a good writer, you shouldn't fear anything. Basically, it just expresses the fact that that only 5% of people are on the 95th percentile.
- gizmo686 14y agoIsn't it saying something more like: only the top 5% of people are worth reading.
- wtracy 14y agoSome people are elitist snobs. Get over it.
- jonnathanson 14y agoI'm inclined to share your skepticism. It's virtually impossible to write a truly good book in three days. That being said, I give him a lot of credit. I give him credit because the hardest part of writing a book is writing a freakin' book. Anyone who's ever seriously attempted the exercise knows that much. You have to overcome ten million types of personal inertia to get started, and ten million types of friction and resistance in order to keep at it. There may be no shortage of bad books out there, but there's a substantially larger number of unfinished books. The latter problem dwarfs the former. While I haven't read his book, and I can't say for certain what his thesis may be, it seems to follow the "move fast and break things" philosophy. If that's the case, then it seems fitting he put his money where his mouth is, and wrote the book in the spirit it is intended to convey. We'll see if it's actually worth reading. But even if it's not, hey, at least he did something. He may have succeeded, or he may have failed, but he got started. I hope he's got more books where this came from, and that each one gets better as he progresses.