First, there are lots of (read: too many) typos in the text; and you'd expect an author of a programming book (who preaches the absolute necessity of accuracy when typing code) to proof-read his manuscript properly. This was not done and in some case, the careless typos can be misleading (an example was provided by another reviewer here, but there are lots more). And if you think typos dont matter, then you do not have the mind-set of a programmer. Stick to Photoshop. Second, the exercise files are often already completed, and because of the occasional incoherence in the order of completing the code samples in the book, this makes the exercise files largely useless (and confusing) if you wanted to use them as starting points.
Now, there is nothing wrong with having a complete set of project files, or the final versions of code/script files for those who want to compare end results. However, the 'norm' or best practice (I would argue) is to encourage readers to have a go at writing as much code by themselves, including creating the C# files and naming them. Instead the author makes reference to existing scripts which when opened are full of completed code, which does not incentivize the need for you to type your own scripts (i.e. what coding is all about). But even if you created such scripts by yourself from scratch, you will often be frustrated because each scripts is linked to one or more game objects but he does not explain which script you will need to attach to which game object (by drag and drop). Without properly linking to the scripts to specific Unity game objects, it is just another C# tutorial book, and not a fantastic one even. Although, I give credit for the excellent coverage of C# language and programming in general in Chapter 1.
Anyway, I find it surprising that even though the book is about the scripting aspects of Unity3D, the author has not bothered to explain some basics of Unity IDE to get someone going. For a book that is over 600 pages, a mere sub-section (2.3) is grossly inadequate because without understanding Unity properly, all the coding you do is a means to an unclear end. At least a chapter could be allocated to this aspect. Fundamental things (like what happens in the background when you drag a C# script file to an object in either the hierarchy or the inspector) are very essential to making your code work - and making meaningful games. There should be explanation on things like WHY we attach a 'Player' class/script to camera objects, etc. In other words, there is too little about the Unity IDE itself at the expense of general C# coding practices. Also, the author does not 'encourage' you to actually type the various bits of code, because he regularly says things like "I've added the following code to Update() function...". In other words, he usually sounds like he is explaining why the code found in completed sample scripts (and pages of the book) are there, but instead, he ought to TELL you specifically exactly what you need to type, where, when and why. You are often not sure whether you are supposed to 'read or review' a particular code block or actually type some or all of it. The author could do better in taking your hands and guiding you each step of the way.
Overall, I believe the book was conceived with very good intentions to teach C# via the Unity IDE, but the sheer number of typos, inconsistencies in how the code examples build up towards a logical end; the lack of clarity of when/what you should type; as well as lack of helpful 'starting point' exercise files means it falls short in many regards. The book should be thoroughly, nay, massively revised if at all a second edition is planned. You cannot expect to teach/learn C# for Unity Designers (beginners) when a lot of the coding aspect is problematic to follow in either the book vs. the sample scripts. Intermediate or expert programmers could probably figure their way out around the problems but the title and content suggest it was written for beginners in Unity coding. In the end, I had to abandon the book three-quarter way because of the multiple issues.
I can understand why another reviewer (Stuart Lee) is returning the book. I will keep my copy for sheer amusement and as an example of how NOT to write a programming book. Besides, even if I wanted to return it, I have over-annotated the text, typos and inconsistencies to the extent that it is already a low value second-hand value book already, even though I had it for just 7 days.
Download the free Kindle app and start reading Kindle books instantly on your smartphone, tablet or computer – no Kindle device required.
Read instantly on your browser with Kindle for Web.
Using your mobile phone camera - scan the code below and download the Kindle app.
Follow the Authors
Something went wrong. Please try your request again later.
There is a newer edition of this item:
Learning C# Programming with Unity 3D, second edition
£130.00
(10)
Usually dispatched within 6 to 7 months
£130.00
(10)
Usually dispatched within 6 to 7 months
