The New Turing Omnibus: Sixty-Six Excursions in Computer Science [A. K. Dewdney] Sold by: Green Street Books-Employment for Adults with Special Needs. The New Turing Omnibus: Sixty-Six Excursions in Computer Science Reprint edition Used books may not include companion materials, may have some shelf. The New Turing Omnibus book. Read 18 reviews from the world's largest community for readers. No other volume provides as broad, as thorough, or as access.
|Language:||English, Spanish, German|
|Genre:||Children & Youth|
|Distribution:||Free* [*Registration Required]|
Singapore largest bookstore offering books, magazines, music, CD, Manga and Updated and expanded, "The Turing Omnibus offers 66 concise, brilliantly. The New Turing Omnibus: 66 Excursions in Computer Science The book is designed to appeal both to the educated layperson and to the. Book. Bibliometrics Data Bibliometrics. · Citation Count: 5 · Downloads ( cumulative): n/a · Downloads (12 Months): n/a · Downloads (6 Weeks): n/a.
This classic biography of the founder of computer science, reissued on the centenary of[ Though they never met, their lives strangely mirrored one another--both were brilliant,and both met with trag[ This book is the definitivecollection of commemorative essays, and the distinguished contributors have expertise in such diverse fields asartificial intelligence[ To trueKlingon TM warriors, no occasion is more sacred than the Day of Honor, when they pay homage to all that makesthem Klingon.
But honor can take many forms Saratchandra Chattopadhyay iswidely acknowledged as one of the greatest Indian novelists of the twentieth century. His novels, serialized inperiodicals and later published in book form, established him as Bengal's master storyteller.
Even today, sevendecades after [ These are Orcs with a difference. These Orcs are heroes. The material was so superficial that I didn't find any additional insights or valuable practice from any topics I already knew about, and those topics that I had little exposure until now were nearly completely opaque from the text. It was weird. The book didn't seem to fit for either a novice or a moderate expert on any of the topics, and the fact that related topics were strewn throughout the book, separated by completely unrelated topics, made it even more frustrating and less helpful.
Maybe if you were using it as a supplement while studying some of the broader subjects for extra practice, it would prove to be of some use, but I'm not even convinced of that.
I have to give this book a solid "no" at this point. There are much better books out there on the subject areas covered here. Patterns of Software This was an odd book, and not at all what I expected. I had expected a book relating advice to the reader on how to design and develop software.
What it is instead is an extended comparison of Christopher Alexander's work on patterns in architecture to patterns in programming followed by speculations on programming languages, advice on learning to become a good writer, and a significant part of Richard P. Gabriel's life story. It was a strange mishmash of things that didn't quite hold together as a cohesive book.
Throughout the first part on how Alexander's books—the most well-known being A Pattern Language—relate to programming, Gabriel quotes Alexander extensively, to the point where I almost felt like I was reading Alexander more than Gabriel. He also did not spend enough time tying all of these quotes into programming and software, so much of the time I was left wondering if the book was just a review of Alexander's works.
Gabriel did have some insights into programming that resonated well, such as Maintaining compressed code requires understanding its context, which can be difficult.
The primary feature for easy maintenance is locality: Locality is that characteristic of source code that enables a programmer to understand that source by looking at only a small portion of it. Compressed code doesn't have this property, unless you are using a very fancy programming environment.
We must be careful to strike the right balance when coding so that we don't unnecessarily obscure things that should be simple and easy to understand just for the sake of abstraction. Sometimes it's better to lay out a process linearly so that it can all fit on the screen at the same time instead of slicing and dicing to the point where the poor sap who has to debug the code needs to chase the flow of execution through dozens of functions and variables across tens of files.
We get about 5 pages per topic and of I own this book for over half a decade. We get about 5 pages per topic and of course that can't be enough to fully explore each one. For a lot of those it's not even enough to explain the basics. I think that aiming for this naturally resulted in either tedious or incomplete chapters.
Other approaches could be more entertaining or even informative. How about assuming prior knowledge - it's a CS book for CS graduates anyway - and instead of trying to explain things just tell some anecdotes, some of the back story that never gets much focus? Or zooming into one peculiar application? I would enjoy reading that.
Of course that's just the opinion of a failed reader of this book. I know some very smart people who loved it. It may be that this is just not for me. It was very difficult to grasp the concepts that were cramped into the 5 short pages but in fact were each worthy of a page book on their own. This is especially true when you have no prior knowledge of the topic; the proofs and statements become quite unclear.
However, my hope is that one day, as I become an expert computer scientist, I can understand it all. Great coffee table book. Explains crucial concepts in computer science like decidability and logic in language arts smart high schooler could understand. Dec 17, Peter rated it really liked it Shelves: I guess it's not for everybody. I like the idea of this book very much. The execution is alright, although I will admit that there are a few chapters that I don't like much. But overall it's a fascinating sample platter of pieces of what we call "Computer Science" and it's all in one place.
I especially like his introduction to theoretical electronics and the computer he designs from scratch. There are a few mistakes in the drawings and micro programs, but overall it's a neat design and you ca I guess it's not for everybody. There are a few mistakes in the drawings and micro programs, but overall it's a neat design and you can actually cover it in a single lecture with your students.
I wish Dewdney would prepare a new edition that fixes the bugs, removes the sad topics nobody wants, and reworks the rest to be even more friendly to the reader.
Then we'd have a nice one for a broad "Intro to CS" course. Took me a good month to get through this one. Lots of bite-sized topics in CS theory. Many topics such as the details behind the undecidability proof behind Kolmogoroff complexity had me spending hours finding supporting information on wikipedia and the like. This book could certainly benefit from a new edition that better motivates some of the d Took me a good month to get through this one.
This book could certainly benefit from a new edition that better motivates some of the discussions e. FFTs , and replaces some of the examples that are showing their age Quad trees, Perceptrons, etc. Sep 19, Will rated it it was amazing. This is a very good introduction to computer science. Each excursion is a problem or a subject area within computer science. Each one is presented in such a way that the reader is encouraged to have a go themselves, and the questions that accompany each excursion often involve writing small computer programs to explore the ideas involved.
After reading this you will have a good idea of both the breadth and depth of computer science, and you will know which areas interest you and which do not. Goo This is a very good introduction to computer science. Good to read just before starting an undergraduate degree and a good "light read" during.
I'm not exaggerating when I say that this book really is exhausting. It has definitely something to do with the format. The book consists of disparate chapters and after finishing one, the next title immediately gets your attention and you have to go on despite your tiredness.
I've been looking forward to read this book for already some time.
It is hard to get through, but it's worth it. Dec 24, Jean-Luc rated it did not like it Recommends it for: I received this book as a Christmas gift after reading a review by Jeff Atwood.
I was surprised when I found it disorganized and turgid, but I trudged along thinking, "If Atwood liked it, it must be good. It turns out Atwood does not read the books that he reviews. I made it halfway through before I decided enough was enough. There is only so much time in the world, and there are much more enjoyable books out there.
Apr 21, Tom Emerson rated it did not like it Shelves: The concept of this book is a good one, and I think the author makes a strong attempt at producing his vision. Unfortunately the result does not live up to expectations.