Computer Science Books

If more people took the time to educate themselves about horses and horsemanship in general and Xenophone's book in particular, perhaps we not see so many "show horses" of various popular breeds so physically manipulated by in breeding for only one or two specific traits rather than breeding for the whole horse. What was true in Ancient Greece is truer still today - without good feet, balance in the body and common sense a horse is worthless. Bravo to Amazon for bringing us this excellent book dirt cheap!

The material in this book is thousands of years old but amazing in how modern the approach is to horsemanship. Most of Xenophon's advice is timely even today. It shows how little has changed over the centuries.

This is a must if you are passionate about horses. It is so clear and to the essential point that it is a pleasure to read.

Xenophon covers several aspects of horsemanship, from grooming, leading, and choosing a horse, to mounting, riding, and training a war mount. Very, very interesting to see what is still applicable today. While this isn't a "training" or even a "horse care book," its a great historical reference from those interested in how horses we cared for and trained 2000 years ago. However, for those looking for a story or a book to teach riding skills, I suggest you look elsewhere. Those interested in dressage will find this worth-while, as it is considered the oldest text on the subject.

Xenophon's philosophy and many techniques, though tailored for the development of a war-horse, demonstrate the ageless capacity for human empathy toward the horse. The horse centered work makes the goal of a harmonious partnership attainable. The book interweaves aspects of barn management, riding technique, and early human psychological insights. The translation keeps this work relevant and vibrant. The overriding theme is one of responsibility for the education and wellbeing of the horse. It is, if nothing else, a comfort to read that some horses in the ancient world were treated humanely in the training process...even if under the unfortunate auspices of a warrior culture. Kurt Hartle, Reydon,Suffolk. UK

Do you want to learn really how powerful CSS can be? This book takes you from the ground up and helps you to understand not only the how to use css for layout but also why you use css. Starting off with the basics you get a good feel for how to write css in both the page itself as well as in an external stylesheet. The authors also explain the advantages and disadvantages of each way to include the styles. Then the book takes you through typography, which unless you are already an expert, you will gain a great understanding of exactly how the type settings really work with the text on a web page. Next, it dives into how to use the css to control your page layout with many different known techniques. You also will understand how these designs work so you can review them and walk away with the knowledge of how to leverage existing patterns and modify them to your needs. If you want to know how to design a page using css definitely get this book.

I have seen this book as very good reference for css. I just would like to have CD also with samples. It is must buy.

I had hoped to use this book as an introduction to using CSS and to help me update my online portfolio. While I did learn a good deal about CSS, this book was not nearly as easy to use as I had hoped.
First, a significant portion of the book is dedicated to a lengthy and repetitive sermon on why CSS is superior and should be used for all your presentation needs. It seems to avoid discussing the shortcomings of the system, or point out where you might need to resort to other solutions, such as JavaScript.
I am a person who learns by analyzing examples and learning to expand on the ideas in them. This, I think is where this book fails. The code samples in the book are incomplete and presented as fragments interspersed with explanation. The more advanced examples are so full of hacks to make presentation identical on all browsers, that they become unreadable. And the final straw was when I downloaded the dynamic-looking photo browser pictured in Chapter 12 and found that the dynamic functions simply don't work! (samples available at http://www.friendsofed.com/download.html?isbn=159059231X).
This is probably a good source for a designer already familiar with CSS. For a beginner, I recommend looking elsewhere.

This book does an excellent job of explaining CSS. My main focus is seperating content from presentation being my sites are search engine friendly.

Great for CSS beginers, I found everything here I needed to know to get started.

My professor used the 5th edition in the Digital Elec class many years ago. I write software but have been trying to make the transition to logic design ... picked up the latest edition for refresher

Great book

You can gain the basic digital logic design knowledge using this book in no time! that is not always sufficient for people who wants to get A grade rather you can just make it your introduction and so soon move to part two (that is up to your current course).
My advice is : get this book unless you have passed this level!

This is the best book to understand Digital Electronics with clear and simple explanations. The salient feature of this book is that it has lot of applications sprayed throughout which keeps the reader attentive and interested. A "Must Read" for graduate/undergraduate students in any university in the world.

I used this book for a course on Digital Electronics. Its great. The book has a great typeset, clear and crisp fonts that go easy on the eyes, well structured (such that you read what you need in order to understand the next chapter). The book is illustrated with apt diagrams. I would consider this book to be beginner-intermediate. This book is a good starting point for learn digital stuff, and a good reference after you learn digital stuff. Its hard to find a book as good as this one.

This is the best book to understand Digital Electronics with clear and simple explanations. The salient feature of this book is that it has lot of applications sprayed throughout which keeps the reader attentive and interested. A "Must Read" for graduate/undergraduate students in any university in the world.

One of the best books on taking an outside look into how we do business, live and experience the world as people, not just consumers.Get Back in the Box: Innovation from the Inside Out

I have read tons of books on business practice and ethos. Rushkoff brought a great mix of theory and practical examples that are working in the real world of business. This book is the business version of "positive psychology", which advises that we develop our strengths and most problems will self correct. In this case it is, pursue your deepest values and you won't have to spend all your resources on marketing. I highly recommend this book for anyone who is involved in an organization at any level. I am a pastor of a church and it has provided many thought provoking concepts to explore in our context.

I'll admit, it took me awhile to really get into this book. Once I got through the first couple of chapters of "Get Back in the Box" though, I couldn't wait to read more of it.

The author, Douglas Rushkoff, feels that we're in the midst of a renaissance in creativity and collaboration. As he puts it, "genuine creativity is a result not of out-of-the-box thinking, but of true expertise." Here's a great example he used partway through the book: The person that decided (years ago) to put a VCR and TV into one device wasn't really innovating. The person who came up with TiVo, on the other hand, was a genius and someone who truly had a handle on people's viewing habits.

He's got an entire chapter on what he refers to as "social currency." The retailers featured as noteworthy examples in this chapter include B&N ("the store is a social hub"), Guitar Center ("it's a place to try out pretty much any piece of musical instrument there is--and to play on it for hours") and the Apple Store (described as "a little cathedral"). I tend to think Starbucks fits the mold as well. In fact, this chapter got me wondering about what would happen if Starbucks and Apple ever decided to create some co-branded shops...

Here are a few of the other interesting tidbits I highlighted throughout this book:

** ...customers don't want to communicate with brands anymore...they want to communicate through them...

** Although we claim we want more leisure time, we are much more likely to find an opportunity for genuinely fulfilling engagement and learning at work.

** It's about learning to tinker, to tweak, and to test the most basic, underlying assumptions of one's core business or technology.

** (Regarding focus groups...) In the vast majority of the dozens of groups I've observed or led, the purpose was less to glean new insights than to confirm the insights already held.

This turned out to be a very enjoyable book with all sorts of great observations.

A great book. Reading this was like a breath of fresh air and really changed my thinking about technology, innovation, design and the hope for creating a livable world.

Where to start...

I rated this 4 stars; 5 stars for being thought provoking and reinforcing my notions of what businesses should be concerned with, and 3 stars for the authors glaring examples of old-renaissance ideas/execution that didn't/don't work, yet providing nothing more than hindsight.

I agree with the previous post that the first half of the book was better than the second half. There are so many examples that are counter to the authors examples, but I'll give a few here.

First, in the absense of fullfilment opportunity exists. While Wal-Mart may be an evil company for some of its practices it also provides people in developing countries with a job, where none may have existed before. If you have no food and someone gives you a scrap then you at least survive to move onto a larger portion. If those who are employed at Wal-Mart cannot find another job that pays more than minimum wage then I would suggest going to a library and start learning...it has free internet access...

Second, many of the arguments made throughout the book are based on a circular reference that is incapable of breaking down, when in fact it would break down. If a=b=c=d...y=z and z=a then for values of a-z that fluctuate so does the continuum. Every example given in the book relating to whatever currency units are give follows the same principle: that at some point, hidden beneath the guise of logic and play, energy will need to be expended that is not optimally or even close to optimally what any person would normally do in search of or in realizing the new renaissance. This breaks the whole model and I suppose it also degrades innovation at the same time.

Third, open-source software, though trendy, has limitations. Imagine a world where function a is performed via single open-source project composing of a single developer, then fast-foward t years where function a is now performed by 1000 different projects each with 1000 developers (who share the same egos), in the meantime you have some number of function a demand satisfied by 1000 projects so a/1000. All of the sudden you have function b that people just though of at t+1 days, but only a small portion like 1% of function a projects are compatible...but the developers of function a projects not wanting their egos to be crushed realize this and perhaps migrate over to the small % of function a projects that are compatible...leaving the other 99% of function a projects to be picked up by some developer(s), whos egos aren't as big, to try and work something out with function b compatibility. Now you have function a compatible projects with a huge number of developers wanting to make their mark with function b, but the 99% of the people who utilize function a and now function b must switch to projects that are fully compatible and relearn, etc. The point is that people want recognition, however good or bad that may be, but it's the truth...even authors put their name, photo, etc.

Fourth, I agree that understanding your "core competencies" are very important and understanding the "source code" and "patterns" is nice, but what really got me was how high people must be in order to realize that this is the path to eternal bliss or "play." I mean who in their right mind would choose to clean out a septic tank as a way of "playing" or even perform surgery on someone's brain...just for fun, when you know that someone's life depended on whether you were qualified or not. If you aren't qualified then doesn't that introduce a classe system of sorts? Who would regulate this...would this person think that telling someone they are incompetent was "playing?" It's clear that any system which qualifies someone as being able to perform a specific action, no matter how much fun they might have, is clearly old renaissance and the illusion of new renaissance is just that (not in entirety, but practicality).

Fifth, while some people prefer to solve challenging problems, others would rather just sit around surfing, etc. What do we do with those people? Where would they get their surfboards, wax, wetsuits, food? I'll tell you who...the people that have enough resources at their disposal to just sit back and ponder how the old renaissance is coming to an end in favor of the new renaissance.

Sixth, peoples faith often becomes a paramount influence in the actions they undertake. Some are at extreme ends and radicalize what is otherwise a very moral and just view of how things should be. These radicals often carry out actions against others because their convictions are so strong and so outside of the middle that even if the middle moves it will not be enough so enough will be "encouraged." This artificial skewing leads to others ultimately forgoing "play" in order to build a counter-trend necessary to prevent skewing that is non-organic. In the end you have a reduction in pure innovation (good) and an increase in pure existence. I'm guessing that the author was too busy contemplating whether or not we could he didn't think whether or not we should...

Seven, the book discusses how currency became the demise of society as it pertains to interest, greed, etc. However, in the Paypal example he exalts that business for being upstanding and trying this new thing, but it ultimately fails because of the banks...yada, yada, yada. Anyways, Paypal was earning interest on the float vs. charging money for its service. How is that new renaissance? If we take the banks out of the equation so that interest is no longer accrued then who pays for the hosting, data, maybe it's those people who like to play in data centers. But then, who builds the steel racks, elevated floors, servers, ethernet cables, routers, switches, supplies power, constructs the building, stays up all night trying to figure out why no interest is being accrued :)

Well, that was more of a rant than anything else. I'm glad this book cemented my ideas about open-source software and about how so many company executives are in such disrepair. Innovation...hmmm...whenever I have a bug in software I usually just open a debugging program that I purchased and print-out the portion of code via a printer, utilizing a driver, written by some person of gets off on that sorta thing...but would they do it for free if there other needs weren't being met...I don't think so.

There's a reason why doctors get paid so much money, there's are reason why people do jobs they wouldn't otherwise do, there's a reason why the new renaissance only exists in the imagination of Gene Roddenberry. The have's and the have not's exist today, and perhaps in the 21st century we can combat much of this gap; however, until everyone is content with their existence and opportunity for existence then we will not reach the new renaissance. Indeed, it will only exist where truly innovative ideas take place...our isolated dreams...

This is a great book. By creating a 2D world Dewdney expands our 3D vision.

In reading this book I was reminded of not only Abbott's Flatland (which was the original inspiration) I was also reminded of Charles Hinton's Fourth Dimension and Choas Coincidence and All That Math Jazz.

In each work, the writers effectively used 2D analogies to give us an idea of what 4D space might be like.

What Dewdney did however was to build detail into what has always been a simple model and thereby give greater detail to the potentialities of our vision.

While others have said that this book would be great for mathematicians I would offer that this book is great for anyone seeking to expand their horizons.

As Henry David Thoreau wrote in concluding his Walden: "There is more light to day than dawn. The sun is but a morningstar!"

Read this book and others like it and bask in the light of that morningstar!

One of the greatest books of all-time. I don't want to over-sell it, so judge for yourselves. (heh) Seriously, this is probably the most complete fictional universe ever created. It reads like a dream and when it first came out (and I was a kid) I often wondered whether the events in the book had REALLY happened. It is that well constructed.

Before it originally went out of print I bought two extra copies so that I'd never be without it, I honestly suggest you read it, and if you like it at all - do the same. It will never leave your mind, and you'll be happy about that.

I found this in the ECSU library, and had a wonderful time perusing it when I was supposed to be doing classwork. The only thing disappointing is that it's fiction. Other then that, it's a rather realistic portrayal of some startling events. Putting aside that the computer project come to life thing is pretty obvious, the rest of this stuff is just too original to pass up. Reading the account of two foreign cultures trying to communicate through a computer program, and having the participant on their side being rather of a mystic bent, makes for some very interesting stuff, as simple as kid's adventure, and as inspiring.

I encourage others to pick this book up. It's great for an inquisitive high schooler (as I was) or an adult.

Dewdney does an excellent job of pulling the reader into the story- one feels as if they are sitting there right next to the screen, waiting for the next contact.

Difficult to put down, and difficult to go back to reality afterwards.

When I was in high-school I had a very intelligent and immensely helpful English teacher, who taught me much of what writing skill I possess today. He came in highly excited one morning, to share with us about a new book he'd come across. Evidently, they had, through a computer, discovered an entirely new reality, that was two-dimensional! And this was an actual event, cutting edge stuff.

Well, a few days later, he came in, quite chagrined, to tell us that, as he read further through the book, he realized it was a work of fiction. But his description had been interesting enough to motivate me to read the book.

The Planiverse's reality is that real, and supported by that much scientific and mathematical principle- Dewdney has done his research, to bring us one of the most delightful what-ifs I've found. Imagine reality just like ours, but take out the third dimension. Everything is well supported, every area of life covered, and the drawings immensely helpful. You truly begin to feel for all the characters in the book. But it's not just an exercise in mathematical possibility. It is a rich story, telling of spiritual journey and insight, as Yendred travels to find his answers. And I still remember the ending as grippingly and eerily numinous, as we realize how closely the Planiverse and our Universe are connected, and how limited we are in comparison to the Eternal.

I have re-read a number of books immediately after reading them for the first time. Re-reading well-written fiction is of course a pleasure, but I usually reserve this technique for non-fiction that is hard to understand or very dense, and I may re-read immediately after the first read or months or years later.

This book is the first I have decided to re-read before I even finished it. The information presented is so full of useful knowledge that I realized I would forget most of the points while I was taking in the newer stuff. With the diagrams and summaries there is a vast amount of content here.

I have one small criticism that I'd like to make. The book shows common-sense techniques for project management, and on subjects like this we feel we could do the job based on instinct. I think that the book, instead of being almost exclusively saying DO THIS, should have a few examples of DON'T DO THIS. Stories that involve mistakes and disasters tend to make the lesson more memorable.

I have written several books, and I have rarely been more impressed at how the author handles huge amounts of information.

Anyway, this book is worth five stars.

EDIT: Forgot to mention it, but the book has a dangerous typo. On page 208, the book says "Exclude" but the word intended is "Exude" - in this case, that's almost 180 degrees from the intended meaning.

And a big Hi! to my loyal fans. Glad you trust what I say.

I have been practicing project management/program management and PMO management for 40 years. This is not only a great reference book for all PM's of any sophistication but it should be the Textbook for Technical Colleges and Universities for Project Management courses. I hold it in the same group as the Capers & Jones book on software engineering

I've read 10 books on PM in the last 3 years. Without a doubt this is the most practical one I've read. It takes PM theory and goes much further than other beginner's guides to actually telling you how to do apply the theory in the real world. The mind maps are particularly good. I have used these maps extensively for operations staff training and brain storming for phase planning. Highly recommended reading.

As I am taking the responsibilities of a technical leader, I am being introduced more and more into the concepts of project management, and this book has helped me a lot understanding and getting insights into the subject. Compact, rich, simple, and assumes no prior project management experience. I would recommend it for anyone who is entering a senior position (especially in the software development industry).

This is one of the better books about PMBOK-based ProjectManagement. But what I really miss, is a practical explanation of how to switch theory to reality. For example: The PMBOK defines 44 processes. Some of them have to be done one time (e.g. defining a Project Charter), but many process steps have to be done daily, weekly, monthly and with different participants. So, what I miss is a description how to organize all these processes during a concrete project including a project plan with all these process steps defined as meetings.
This book is a really good introduction to PM and it helps to understand every PMBOK process. But when trying to use this methodology in daily work, you dont know what steps to do with whom and when. I simply miss a kind of project calendar showing how to spread these processes over the timeline.

This is the best book on C++ ever written, even better than Eckel's "Thinking in C++".

It is a very clear book, easy to read, with colors, well organized and with exercises. Solutions are provided for the exercises.

I think the most important thing about this book is it's written with ISO C++ 1998 and STL in mind. Most other books teach you C++ 1989 (or even older!) and have an appendix about ISO C++ 1998 and another appendix on STL, and believe me, that's not good for you.

This is certainly the best C++ book I have read for auto-didactic purposes. C++ is a horrible programming language (coming from a functional programming POV, as well as a ton of ANSI-C systems and Fortran numerics coding in my past), which has unfortunately become a standard in many fields. Should it be a necessary evil to you, this is probably the book to read. Better yet: find a different line of work. All right thinking people should avoid making C++ a part of their profession. It has erased more hours of talent than MS minesweeper or solitaire.

After having purchased and read many different C++ books over the last few years in an ongoing quest for C++ knowledge... I can whole
heartedly endorse this volume... You will learn C++ from this book , buy it, study it , move ahead with your C++ journey...

Attending lectures on C++: Not a clue.

With this book: No problem at all!

The book is great!

If you like to learn from examples and illustrations, and do not have too much time to waste with long explanations, this book is for you. All the major topics of C++ are covered in a nicely structured series of 33 chapters. To name a few:

-Pointers
-Classes
-Methods
-Overloading
-Dynamic Memory Allocation
-Inheritance
-Polymorphism
-Abstract Classes
-Exception Handling
-Templates
-Containers
-etc

Every topic in a given chapter is typically introduced in two pages, the first with an illustration and/or a sample code, followed by a clear and concise discussion of the topic, including its motivation and caveats. The discussion on pointers is particularly illuminating, as well as the discussion on Classes and Object Oriented Programming, which is after all the heart of C++.

I would not recommend this book for someone who does not have any previous exposure to a structured computer language, but it is definetely a great guide and reference on C++ for those already familiar with C, Pascal, etc.

I grew up fascinated by the Hardy Boys series and on occasion I read a book in one of either the Hardy Boys or Nancy Drew series'. I find it fascinating to compare the plot structure and social and historical context between the books over time.
This book is thoroughly modern; Nancy and her friends George and Bess travel to the U. S. Virgin Islands. While there a boy rock band arrives to film a video and suddenly there is danger. There is dissension in the group but that does not appear to be enough to motivate the incidents of attempted murder. Nancy and her friends investigate and discover a crime ring smuggling people into the United States. Nancy gets too close and the ringleader kidnaps and tries to kill her. Fortunately, the resourceful Nancy manages to get free and the people in the ring are arrested by immigration agents.
While Nancy is a bit aloof from it, the girls still react like modern girls to the presence of the rock band. Also unlike the earlier episodes, when George and Bess encounter a man with a knife, they fight back rather than cowering. They kick the knife out of his hand and push him into the water.
Social change is inevitable and the differences in the Nancy Drew books over the years reflect that change. This book is one that will appeal to the modern adventurous young girl as it presents Nancy in a situation of the 1990's and she is cool, capable and determined to have fun.

If you dare to, enter Danger.com, by Jordan Cray. During this adventure on the internet, a boy tries to find out if he has a dad or a mom. He has a best friend and whose mom is his moms best friend. He finds out where the guy works that could be his father. This book is like when you get thrown upside down on a rollar coaster. You're excited and scared at the same time. It's a thrill and a chill, and you don't know how to cantain yourself for the ride. While all this is going on, he gets so into finding his dad that he and his best friend start to drift way from each other faster and faster. They have no control over their friendship. I use to be friends with a girl, but after Junior high school we drifted apart. We still see each other, but we are neighbors. He has time to make up for what he did wrong. If you like adventure, or mystery you would like this book. I recommend for people that have lots of things going and know how to juggle all them together. If you know what it's like to try and try but still not do good, then you will enjoy Danger.com.

When I think of reading, I think sleeping, yawning and boring. They make us read every single day. Their torchering us. And they say reading is good for your mind and for your health. I think bla bla bla. Get those books away from me. Groose! Now that I'm a teenager I know I need to extend my vocabulary to it's greastest point. Or I wont get any where in life. I was in the library one day looking for a book to read. I picked up a book called danger.com. It sounded interesting. I started reading it and it was an amazing book. I loved it. The best!!!

It's about this really smart 17 year old guy. He gets in trouble. Meets agirl. Thinks his moms crazy around the end of the book. Then him and his mom our very happy at the end. They have a normal life. Terrific book. I've only read 1 or maybe 2 books that i had enjoyed. But i'm glad that I liked reading it because I want to try to extend my vocabulary to it's highest point. Read it. I promise you wont fall asleep.

I just finished reading this book and I loved it. I don't want to give the whole story away, but it is about a boy who has a whole bunch of lies told to him(even by his mother) and is wanted to work for some hackers to take over the world. You think you know the story at first, but it twists around at the end and it all adds up. This is a must read for people who like mysteries and computers.

I found this an exellent book. The original design patterns book drew its examples from C++ applications. I could see a use for the patterns in C++, but I thought most of them would not have been necessary if the code had been written in Smalltalk.

This book did an excellent job of showing how and where the patterns could be used in Smalltalk applications. The authors also extended and clarified many of the pattern so that they were simplier to understand. The book is more than a companion to the GOF book; it is an enhancement of it.

This book gives you a better understanding of the patterns than in its original version (the GoF one). I am not a SmallTalk programmer but a 9 years C++ one. At work I had to use the GoF book and never liked reading it. In contrast to this, the SmallTalk companion is easy to read and you can understand the patterns within the first few lines of their description. Take the Bridge pattern and compare their discussions in the two books. If you really like the Gof one then buy it. But according to me, it would be a big mistake buying the GoF in favour of the SmallTalk companion. Trust a C++ programmer :-)

This isn't a Smalltalk translation of "Design Patterns." Instead, it's a companion to that book. You'll need to read the first one to get the most out of this one. If you have read the first one, you'll find this one is better written and really casts essential light on some of the GOF material. The Smalltalk aspects of this book are really a non-issue (except perhaps showing static-typers how many hoops you don't have to use in Smalltalk). This is required patterns reading.

I bought this book because of the unresolved questions I had after spending so many hours exploring the GoF original book. I am an experience C, C++, and Objective C programmer, not a Smalltalk guru at all. And I found the GoF very confusing and intimidating. My current projects these days are written in Java (I miss Objective C). I looked for a book that would cover the pattern catalog in Java because I was really questioning the purpose of some of them in that language. Creating some mechanism to overcome the C++ language is somewhat understandable, but why bother with Java. Take the prototype pattern for example: "...It's (the prototype pattern) less important (to use it) in languages like Smalltalk or Objective C that provides what amounts to a prototype..." (page 121) Sure, ok, but what about Java? Can you give me an example on how it would benefit a language that doesn't really require it like Obj C, or even Smalltalk? Then the sample code refers to the maze example but not much material is given here. I bought several books with Java and Design Patterns in the title but was very disappointed with the beginner level these books approach this problem. The titles are seductive but the content is not that great. I don't need another ADOO (I've read Larman's book already. Get it if you are new to OO BTW.) So I ended up getting that book as a last resort. And you know what? It's great. I program in Java all day (and sometimes all night, sigh...) and this book spends more time on my desk than the GoF original one. So, if this comments remind you some of your experience, you should give this book a try. And this book lighted up another bulb in my brain: I ended up downloading Squeak and prototyping in Smalltalk some of my projects just for the fun of it, but that's a side effect I guess ;-)

I found this an exellent book. The original design patterns book drew its examples from C++ applications. I could see a use for the patterns in C++, but I thought most of them would not have been necessary if the code had been written in Smalltalk.

This book did an excellent job of showing how and where the patterns could be used in Smalltalk applications. The authors also extended and clarified many of the pattern so that they were simplier to understand. The book is more than a companion to the GOF book; it is an enhancement of it.

It describe all aspects about digital crimes using a clear language. It's very good for neubies.

If you are new to this world this is where you should begin. Digital Evidence contains all the knowledge one could amass by obtaining PHD in computing. Especially when you don't have time for a Diploma. I have bought 5 books pertain to digital crime from USA and UK. But this is the one and only book I am recommending to any one in any continent who want to learn or new to this arena. All the other books in this field for Attorneys or with similar requirements are some what academic and may be boring. The CD-ROM accompanying the book gives you much needed hands on training, otherwise which will cost you at least US $ 4000, if you are to go to a training centre to do the same.

Sometimes, defense attorneys have it easy: one slip-up by the prosecution and evidence is thrown out. Knowing that, law enforcement goes to great lengths to ensure that evidence is appropriately collected and protected. That works well in the physical world, where law enforcement has many generations' worth of experience. But in the modern world of computers and digital networks, where the simple act of rebooting a computer is enough to wipe out large amounts of evidence, law enforcement clearly needs thorough guidance.

Such a resource is here: Digital Evidence and Computer Crime, an excellent book that details the elements of digital crime. Author Eoghan Casey does a superb job of applying forensic science to computers. The information presented here is critical to a diverse audience: law enforcement, attorneys, forensic scientists, and systems administrators, for instance.

While cybercrime law is in some ways similar to other aspects of criminal law, it nonetheless has its own language and categories. For instance, jurisdiction is a key element in both the physical and digital realms, but it is a much trickier concept in the latter. Casey develops this topic and many more. Those new to computers and networks need not worry: the book begins with an explanation of how they function. With the basics out of the way, Casey details how computers can be used in crime and how the evidence created from these activities can be used for later analysis....The accompanying CD-ROM contains simulated cases that integrate many of the topics covered in the text. In all, the book and CD are an excellent introduction to an increasingly important area of law enforcement.

This is an excellent book from a real expert.

Everyone and their brother are writing books about computer security and digital forensics.

The difference here is that Eoghan Casey knows what he is talking about.

Excellent book!

This text was used for the digital evidence and computer crime class that I just completed. The book is clear and easy to understand. It goes into detail only when needed. I was concerned that this information would quickly become out of date, but the ideas presented are current and provide a solid background for understanding any newer technologies that come down the road. I usually sell my books after the semester ends, but I have decided to keep this one.