No, I don't know the reviewer (or at least I don't recall having any connection with him - I've met a lot of people over the years).
And no, I too wouldn't give it a 10. There's always room for improvement.
But in terms of the criteria by which you would judge this, I'd place other factors over technical accuracy. While I certainly made every effort to be accurate and timely, my top priority was to make sure it was understandable to the average computer user, starting from about age 13. That included making it entertaining enough so my readers wouldn't use it as a cure for insomnia (a problem all too many technical books suffer from).
The real measure of success for this book is whether people reading it can understand it and use what they learn to make their computers more secure.
Just in response to some of the comments I've read so far:
Teen's don't care... Many don't. But they, like home users in general are have huge problems with regards to security. So what do we do? Just give up? We (and this includes all the knowledgeable teens) have to do what we can to improve the situation. This book is my contribution to the effort.
Better taught in person than from a book... I agree, but many parents don't know enough to teach security - their kids know more than they do. In those cases I actually suggest flipping it around: teens, teach your parents! I've met a number of teens who have thier security act together - more who just think they do:-)
Parents and grandparents are a better audience for the book... I've gotten some very nice emails from adults and seniors who find it very readable.
The title is a gimmick... Sure, but you'll remember it, right? Actually, the title was the idea of a group of teens. I never would have come up with it on my own.
I just published my 8th eBook. They're sold on Amazon.com, desaware.com and componentsource.com. These are actually what Amazon calls eDocs - PDF files that are printable and don't use DRM.
I believe there is a real future in this form and value both for authors and readers - at least in the technical arena. But the value is primarily in the 25-100 page range.
From a reader's perspective:
How often have you bought a technical book only to find that you only really need one or two chapters? A 25-50 page eBook can address one specific topic in depth, and at a lower price than the full book.
A shorter work can be published in a timely manner. I can write on a topic and publish it in a few weeks - not the 6-9 months that a print book would take.
For those who don't like to read on a screen, All Amazon eDocs are printable, and at this length it isn't unreasonable to print on a home printer.
From an author's perspective:
Right now traditional markets for authors are articles - which are typically 5 pages or so, or full books. An eBook allows an author to go into far more depth than is possible in a magazine article, without the hassle and effort of writing an entire book.
It is true that at this time the business model for eBooks is poor - I believe it's in part because many people don't see the value of the format. But I think the argument for eBooks, or print on demand (once that technology matures) is compelling for both readers and authors at the 25-100 page range - at least in the technology arena.
Dan
Re:Sometimes it can save your life
on
Hijacking .NET
·
· Score: 1
This statement:
"Isn't it stupid to rely on private methods when robust solution may take just days."
Strikes at the heart of the question. As a software designer, I totally agree with you. But as a software engineer, I'm also concerned about economics. If my cost to the company is $75/hour, do I choose the $300 solution, or the $2000 solution?
Ok, you might say - but what about the long term costs? It will cost much more to fix the problem later when MS breaks it, right?
Not necessarily. Because you can bind your app to a specific framework version, your risk of a sudden expensive break are slim.
But aren't you just deferring the problem? You'll want to update your software for the next version and you'll have to write it then, no?
Well, maybe not. Because MS will probably have a canned solution that, if you use propery OOP design, you'll be able to plug in easily.
So, we might well be talking lifetime cost savings of thousands of dollars here.
The purist in me dislikes this approach. But is that enough to write off these potential savings?
That is the question.
Some clarifications
on
Hijacking .NET
·
· Score: 2, Insightful
I've enjoyed reading the many comments so far (well, most of them). Just a few clarifications:
1. I am not anti-Microsoft. I thoroughly enjoy coding in.NET. The eBook is not anti-Microsoft or anti-.NET
2. This eBook does not break.NET security or demonstrate a flaw in.NET security. It does, however, teach an important point - that member visibility is not a security boundary. Failure to consider this could result in a developer doing a security Assert within a private member and inadvertantly create an exploitable security flaw in their code - which is an extremely serious issue.
3. This is not a design flaw in.NET. Private member access is necessary for object serialization in.NET and is itself secured via code-access security.
Slashdot Mirror
"Backups: The most important thing you'll probably never do"
Dan
And no, I too wouldn't give it a 10. There's always room for improvement.
But in terms of the criteria by which you would judge this, I'd place other factors over technical accuracy. While I certainly made every effort to be accurate and timely, my top priority was to make sure it was understandable to the average computer user, starting from about age 13. That included making it entertaining enough so my readers wouldn't use it as a cure for insomnia (a problem all too many technical books suffer from).
The real measure of success for this book is whether people reading it can understand it and use what they learn to make their computers more secure.
Teen's don't care... Many don't. But they, like home users in general are have huge problems with regards to security. So what do we do? Just give up? We (and this includes all the knowledgeable teens) have to do what we can to improve the situation. This book is my contribution to the effort.
Better taught in person than from a book... I agree, but many parents don't know enough to teach security - their kids know more than they do. In those cases I actually suggest flipping it around: teens, teach your parents! I've met a number of teens who have thier security act together - more who just think they do:-)
Parents and grandparents are a better audience for the book... I've gotten some very nice emails from adults and seniors who find it very readable.
The title is a gimmick... Sure, but you'll remember it, right? Actually, the title was the idea of a group of teens. I never would have come up with it on my own.
For more info including the book's introductions visit http://www.alwaysuseprotection.com/
From a reader's perspective: How often have you bought a technical book only to find that you only really need one or two chapters? A 25-50 page eBook can address one specific topic in depth, and at a lower price than the full book. A shorter work can be published in a timely manner. I can write on a topic and publish it in a few weeks - not the 6-9 months that a print book would take. For those who don't like to read on a screen, All Amazon eDocs are printable, and at this length it isn't unreasonable to print on a home printer.
From an author's perspective: Right now traditional markets for authors are articles - which are typically 5 pages or so, or full books. An eBook allows an author to go into far more depth than is possible in a magazine article, without the hassle and effort of writing an entire book.
It is true that at this time the business model for eBooks is poor - I believe it's in part because many people don't see the value of the format. But I think the argument for eBooks, or print on demand (once that technology matures) is compelling for both readers and authors at the 25-100 page range - at least in the technology arena.
Dan
"Isn't it stupid to rely on private methods when robust solution may take just days."
Strikes at the heart of the question. As a software designer, I totally agree with you. But as a software engineer, I'm also concerned about economics. If my cost to the company is $75/hour, do I choose the $300 solution, or the $2000 solution?
Ok, you might say - but what about the long term costs? It will cost much more to fix the problem later when MS breaks it, right?
Not necessarily. Because you can bind your app to a specific framework version, your risk of a sudden expensive break are slim.
But aren't you just deferring the problem? You'll want to update your software for the next version and you'll have to write it then, no?
Well, maybe not. Because MS will probably have a canned solution that, if you use propery OOP design, you'll be able to plug in easily.
So, we might well be talking lifetime cost savings of thousands of dollars here.
The purist in me dislikes this approach. But is that enough to write off these potential savings?
That is the question.
1. I am not anti-Microsoft. I thoroughly enjoy coding in .NET. The eBook is not anti-Microsoft or anti-.NET
2. This eBook does not break .NET security or demonstrate a flaw in .NET security. It does, however, teach an important point - that member visibility is not a security boundary. Failure to consider this could result in a developer doing a security Assert within a private member and inadvertantly create an exploitable security flaw in their code - which is an extremely serious issue.
3. This is not a design flaw in .NET. Private member access is necessary for object serialization in .NET and is itself secured via code-access security.
Dan