Software Books

This book is not for the faint of heart in Access 2000 coding but it is invaluable to the advanced programmer. I refer to this book almost daily in developing our in-house applications. The real strength of this book is in developing code that is more portable or reusable. I have gone from writing sloppy code that is application (or even form) specific to writing completly reusable (and of course fully documented) code. Excellent reference for the power VBA programmer!

Had everything I needed to get going, even the obscure stuff.

Only thing missing was an explanation of what Access does with it's version of Stored procedures, but then again, Microsoft isn't sure on that one itself, so that's no surprise.

Great book, I recommend it.

Love this book. This is the only book I know that does not abandon DAO. I like DAO. All other post Access 97 book abandons DAO.

It is well written and have used many of this examples for my job. I even like it better than the Getz books.

I BOUGHT NOT LESS THAN 15 MS ACCESS BOOKS WHILE LEARNING ACCESS. I FOUND THIS ONE MOST HELPFUL. I HAVE LEARNED MANY THINGS FROM THIS VALUABLE BOOK: CLASS MODULES, CUSTOM COLLECTIONS, CUSTOM PROPERTIES & METHODS, API CALLS ETC ETC... THE AUTHOR HAD PROVIDED MANY USEFUL CODES. I REALLY LIKE HIS BOOKMARK TRACKER.

This was just the book I was looking for. Scott goes into alot of the issues that most of the books on Access just do not. For instance his sections on the winAPI's as well as performance recomendations. I found this book a total reference for beginner through the intermediate programmer of Access. Thanks Scott.

i am somewhat new to linux and i am finding this book useful. It is well organized and has most of the commands I am looking for in RHEL 5. Any other books for starters folks would recommend?

This book is a fantastic way to take your tinkering to the realm of true Linux mastery. Christopher Negus has written some of the best comprehensive Linux guides on the market, but here he has slimmed down the advice into tried and true command line tips that -- once you've learned a few of them -- will have your boss singing your praises, and friends calling you for advice. [...]

Do yourself a favor and pick up a copy of this slim, portable, and power-packed book. You won't regret it!

This book is a very good desk side companion. This is not your typical "power users" book that is just a raw dump of a ton of esoteric commands that go in one eye and out the other. It is actually useful commands put into an understandable context, organized by classes of activity. I've been using Linux for many many years yet I'm learning, and using, new things from this book. I would highly recommend it.

If you're looking for a gift for your beloved Fedora/Red Hat geek, this is it. You'll be thanked when the gift is opened, and you'll be thanked each time as the book is used over and over.

--
Jesse Keating
Fedora Release Engineer

This book is practically "perfect" (sorry if sounds exaggerated) for the following reasons:

1 In less than 260 pages (340 considering appendixes) quickly covers a wide and useful selection of topics
2 The text is updated to the latest improvements in EVERY subject
3 Very easy to read and follow with or without a computer at hand
4 Command line oriented

Let me explain:

1 From the Table of Contents you may see the book covers practically everything most users will need when using a Linux as Server or Desktop; that selection of subjects was really well calculated and provides with a mix that is rarelly found. Also, the "depth" for the provided information was carefully calibrated in order to show the most useful situations (by the way avoiding being boring with nerdy configurations)

The authors provide with a minimal and informal introducion to every subject, and next use a good selection of samples for illustration.

2 Surprisingly, all chapters were written taking into account a lot of "modern" improvements in distro/commands/kernel. Every old-Linux user may appreciate here the giant advances made by Linux to the point that practically every subject is now simple to manage (or at least not esoteric.)

3 As I have several years using Linux, most of the material presented was familiar (with a lot of "modern" surprises), but the organization and style did let me follow all the text without needing to test the examples or configurations in order to understand anything. At least for me, it is a big bonus.

4 99% of the recipes and examples apply to the command line (with some mentions to the graphical front-ends). This may be sad for new users, but very important for administrators or users that look for "maximum flexibility", or "task automation" or work in "server environments" where the GUI is not allowed or discouraged.

Hey folks... I've been an RHCE since 2000, training RHCEs since 2003, and "doing Linux" since 1996.

What I like:
The three big things that I like about Linux Toolbox are:
1) It concisely shows you how to use the Linux command line to solve many of the most common personal and administrative tasks.
2) It uses the proven "learn by doing" method to show the reader how to just "get stuff done" from the Linux command line.
3) What really sets this book apart from other "next level" type books is its well thought layout and how they organized the content in a quickly accessible way. Negus & Caen split the content out by Shell stuff, Working w/Files, Text Manipulation, Multimedia, Administration, Backups, Networking, etc.. . Well thought out and quickly useful as an on-hand reference.

So who should buy this book?
I see it being a "best fit" for two groups of people:
1) Technical users and admins who want to become more competent on the command line and be able to do ten times more work thought automation (scripting).
2) Windows power users who want to become more savvy on the Linux side (Linux power user wannabes). Especially those who need to get Linux CLI/shell proficient quickly (such as Windows sys-admins who have had Linux forced on them)

Old Timers Too:
The cool thing is that even if you've been using Linux for years (as I have), there are still useful "Oooo.. cool!" moments peppered throughout the book. Do you know how to properly (and quickly) get the most out of classic power tools like find, sed, awk, case, and tr? Are you armed with experience in all the newer über tools such as screen, dmidecode, growisofs? Do you know how to do software RAID from the command line (mdadm) or know how to build & control LVM via its command line tools? If you answered "no" to any of these.. you should check check out Linux Toolbox.

Negus and Caen have a winner here. Good job guys.

Tweeks

Dr Folk was my graduate advisor and I worked with Bill Z at TMS. This book actually reflects some of the technology we worked with there as well as other thoughtful and useful ideas in storing data on disk.

There are many Computer Science references that show several common sorting techniques but most stop there. This book has what no other that I've seen had: A concise discussion of sorting data that won't fit into storage at once.

It's easy to sort items when you can load them all into memory. Many books show how to do that.

This is the first book that I've seen that explains, in detail, methods for sorting data that is too large to fit in memory at once. Techniques are shown, then refined.

An amazing book. Although it's a textbook, it's an excellent reference for all programmers. Even if you think you know a great deal about file structures and/or sorting data, you will learn something from the techniques shown in this book. I couldn't put it down.

The metodology used by the authors to write the book is really excelent.
Starting every chapter with a very interesting introduction and covering all the aspects of the inteligent design of file structures with many examples in pseudocode. The references to other books and papers in the end of each chapter makes you fell secure. The index of key words (with a small summary) is really usefull, when you finish reading a chapter you can test yourself to see if you really know it (when you have little time, for example, a day before exams, then it's much more usefull). The exercises and programming projects (always using real world problems) after this index closes each chapter nicelly. The book also discusses the problems with implementations in C and Pascal.
The best one !!!
Congratulations to Folk and Zoellick.

Este libro es una exelente referencia al la estructura de archvivos, gracias a como los autores desarrollan el texto, de una manera deliciosa que profundiza en los problemas de almacenar en archivos, poco a poco y profundamente, y lo que es más importante haciendo que el lector se de cuenta de por que realmente la necesidad de cada nueva estructura de datos revisada. La única pena es que ya es un libro bastante viejo yen ciertas lieneas el lector puede pensar que el libro esta desfasado, pero en lo verdaderamente importante, lo que el libro cuenta sigue estando vigente y lo estara por que al fin y al cabo las bases no cambian.

As a senior software designer, I helped implement file structures for dBASE, cc:Mail, Collabra Share and other commercial software packages. I spent 16 years learning this subject, and Folk and Zoellick taught me a few things in addition to presenting the material so logically, so usefully, that no one need write a book on this subject again

The accounting text, it is - what it is. Some might find it interesting, but it was a required, it was good for what I needed =)

This book is awesome. If you don't understand the accounting terms or what is being said in class, then this book will help you supplement the lectures. I recommend this book for students who have to take accounting more then once. It really helps me understand the material and I do have another exam tomorrow. I am ready to take the test.

Conditions of the book was as described (brand new), super fast delivery, very trustworthy, high value product, great service!! I will definitely order from here again!

I found the Study Guide to be a big help when needing to understand a little more than what the Course book tries to teach you. In the guide, there were examples of problems that are not explained in the Course book. The guide helped me to make better grades on my assignments, better grades than what I was making before I purchased it. I really understand the concept of accounting more in several areas of the business. I would recommend any study guide book, in any subject, to any one!

I am taking a condensed Accounting course and was somewhat lost in the first half of the course which is why I purchased this book. Each chapter is summarized and then there are various exercises and examples to work on. The most helpful part is having the answers for each problem right there, so one is quickly able to see where mistakes were made. This book is worth the price. And, if you're struggling with accounting, it will make a difference in your understanding of the material and your grade.

This book makes it easy to fix Access. Simply look in the table of contents for the annoyance that is plaguing your database and go to the page that fixes it. Most of the fixes are simple ones that are either hidden from the user or just not documented well in the Access help. Just one of the fixes was worth the price of the book. The rest were bonuses. My database now works the way I had envisioned it would.

0-596-00852-X
Reviewed: 1st Edition

If you work with Access (or are thinking about it) you really need this book. Access is a very capable and powerful app and can certainly handle the majority of small business needs (and even enterprise class as well, say if you're using Access as a front end to a backend SQL database). The catch of course, is that Access is full of inconsistencies, irksome quirks, weird "features" that don't work as expected, and of course (like all complex software) bugs. (Although to be fair there are many things that MS probably can't change to ensure compatibility with already written applications).

This book notes the weird stuff that can crop up in using Access and more importantly how to work around same.
In my case I had never done any development with Access before but wanted to develop a custom application using it. Before starting however I bought this book - and am REALLY glad I did. There were many pitfalls that I would have fallen into unless otherwise warned (of course at the start it was kind of discouraging seeing all the "issues" one can have with Access, but better to be advised than sorry after!)

The format of the book is primarily a question and answer format, like "I'm trying to do XXX but it doesn't work" with an explanation of what's going on and *why* it's not working and solutions for accomplishing the task at hand (which may include VBA code or diagrams to help illustrate the point). The Q&As are organised into chapters dealing with a specific topic (i.e. Forms, Queries, Reports, Code Modules etc). In the course of my app development I have reached for this book more often than some of the thicker and heavier (not to mention more expensive) Access books, but you will undoubtedly need other books for reference as well (this book isn't a tutorial nor for absolute newbies to database or Access development, even though there are explanations describing normalisation, relationships, etc).

Aside from the Q&As there are very useful tips regarding recommended options to enable/disable ("Access's Bad Defaults"), Optimization ("How can I speed up a slow combo box?") and avoiding database corruption. This kind of "real world" information is exactly what you NEED to know when you do development and is precisely the kind of thing you'll NEVER find in the help files.

There's also other information such as a list of common Visual Basic functions (and what they do) which is useful when you need to do some task but don't know the name of the function. Likewise there's a similar list for Access Events which is helpful in figuring out which event you need to attach code to in order to have something happen. Lastly there's a Glossary of terms ("What's the difference between a bound & unbound control?").

Unlike other books this one doesn't come with a CD. But that's OK, because typically to solve problems you don't need a lot of code once you understand what's going on (in any case code will have to be customised for your app).

If you're developing an application in Access using custom forms, reports, VBA etc you'll get the most benefit from this book. Overall, I think this book's value exceeds the purchase price.

Wow what a great idea for a book series!!

I thought I had seen it all, but then when I picked up my first "Annoyances" book I learned there was a whole new niche out there that had yet to be exploited.

For many of us out there, we pick up technical books for a few typical reasons: to learn a new skill or a reference for an existing skill. What about if you already use an application and there is a whole known set of pitfalls and problem areas that you either need to find a workaround for, or you just want to learn about so if the need arises, you know how to deal with these?

Well, enter the "Annoyances" line of books.

'Access Annoyances' by Phil Mitchell is a great companion book for anyone that has a lot of Access books on the shelf or uses Access on a daily basis and needs to read up more on the problems that will be seen at some point. With a layout that takes each problem one at a time, the flow is very good, and the writing style is clear and concise. Unless you are the MOST experienced of Access users/developers, you will be able to pick up something from this book, and it's more likely that you'll pick up a LOT of things.

Some of the O'Reilly prices on books blow me away because they are so low. It's like you are paying x amount and getting xxxxxx in return. If you use Access on a daily basis, you owe it to yourself to pick up a copy of 'Access Annoyances' right away.

***** HIGHEST POSSIBLE RECOMMENDATION

I wish I had this book when I began programming Access, it would have saved me a lot of frustration. The writing is easy to follow and it contains a wealth of information I had to either learn through trial and error or lots of searching google groups.

That said, there isn't much of value here for someone with a couple of years Access experience--you've already learned this stuff through trial and error or searching google groups!

I only found one piece of incorrect information--it is possible to create page headers on a subreport by creating a dummy grouping level (=1) and putting your headers there. The book says the only way to do it is by putting the headers on the parent report.

I consider myself fortunate that I converted my last regularly used database off of Access awhile back. While the software served me well in learning about database systems when I first made the move to PCs, I always found myself fighting with things that should have been easier than they were. Now I find out that it wasn't just me. Phil Mitchell and Evan Callahan have put together a great book titled Fixing Access Annoyances. If you spend any time in Access, this ought to be on your bookshelf.

Contents: Access Basics; General Annoyances; Performance, Versions, Security, and Deployment; Data, Tables, and Database Design; Queries; Forms; Reports, Mailing Labels, and Charts; Expressions, Macros, Code Modules, and Custom Controls; Appendix; Glossary; Index

The Annoyances series is set up in such a way that each chapter covers a series of "questions" posed as to why a particular software package behaves in a certain way. The questions range from minor "why does Access always do x" to "my #$@%@ database is corrupted!", and the conversational tone between the questioner and the authors is fun to read. After reading some of these things, you wonder why *anyone* would use Access! Mitchell and Callahan, although experts in Access, maintain a healthy cynicism towards the product's features and foibles, and all it would take is for you to find three to five annoyances that bug you to no end in order for you to think this is the best money you've spent in a long time. They also try and cover a range of things, from beginner to advanced level gripes, so that you should see value wherever you are in the continuum of Access experience.

If I had this book available to me a year ago, I might still be running my reading log database in Access instead of in Notes. I certainly would have experienced far less frustration than I did. After making sure you have a solid Access reference guide on your shelf, this should be your second purchase on the subject...

This book is a great introduction to After Effects and Flash. If you have experience with Flash, it will have you creating stunning motion graphics in After Effects in no time.
Chris Jackson's writing style is light and eminently readable. He doesn't get bogged down in a lot of exposition, but instead introduces the concepts needed and then gets right down to step-by-step instructions. His examples are well-thought-out and, rare for books like this, they are actually realistic.
I had never used After Effects before, but this book got me going and up-to-speed much faster than I thought I would. I would highly recommend the book to anyone who wants to get started with After Effects and motion graphics.

I have been learning flash in school and am attempting to learn After Effects. Not only has it been easy to understand and helpful in learning AE, but i have learned useful Flash tips. The set up and pictures helps my "right brain" enjoy the studying process.

I was pleasantly surprised by this book and the included media!

Chris Jackson has hit on the right amount of technical detail and practical content to make this book easy enough for a beginner to follow, while still keeping it interesting for intermediate users. My 11 year old son and I used this book and went through the projects together. We enjoyed it very much!

Highly recommended!

Chris Jackson is an excellent teacher. His classes in After Effects at the Rochester Institute of Technology featured notes that were far easier to understand than standard books on After Effects and Flash, and I always hoped he'd write a book incorporating some of the lessons taught in his classes.
He has, and it's a winner. Most computer animation books are heavy going, but this one is easy and fun to read. There is no waste, no padding, no jargon, just solid information. It is easier to animate 'parented' puppets in After Effects and export in Flash than to work in Flash alone--the enjoyable exercises on the enclosed DVD will have you up and animating your own characters in no time at all.
I can recommend this book to anyone who is interested in hand drawn computer animation.

This book is excellent and I highly recommend it for all animators! There are many tips, examples, and workflows that show exactly how to bridge Flash and After Effects. There is a nice balance of web and video examples and how to properly prep and animate assets for each. I found the chapters on character animation and visual effects most helpful. The examples clearly show how to get the most out of parenting, puppet tools and fractals. I found the examples fun and inspiring. Unlike many books out there, the artwork and examples are well thought out and look great! The book is also well written. All examples were very easy to follow. I commend the author for this wonderful book!

The philosophy behind frames and framing techniques astonishes me. It is revolutionary and practical. I like it very much.

Chancellor C.
http://www.extremephonecards.com

I have pretty much experience with object oriented and procedural programming in several languages, now getting into AOP and byte code engineering. The first 30 minutes with this book were dissapointing - i couldn't figure out what the heck this guy is talking about. So i started at the front, not back cover. And this is my hint - read it from the beginning, page by page. I knew, there is something wrong with software development in general, now i know what it is exactly, and why. I knew it! More - i know how i can break this vicious circle and burn the tires. We've been going the wrong way folks! This definitely is the most valuable book in my monster library (some 100 titles). This is the top secret knowledge, worth thousands and thousands of bucks. I really am not related to the author or publisher. Great stuff!

I have pretty much experience with object oriented and procedural programming in several languages, now getting into AOP and byte code engineering. The first 30 minutes with this book were dissapointing - i couldn't figure out what the heck this guy is talking about. So i started at the front, not back cover. And this is my hint - read it from the beginning, page by page. I knew, there is something wrong with software development in general, now i know what it is exactly, and why. I knew it! More - i know how i can break this vicious circle and burn the tires. We've been going the wrong way folks! This definitely is the most valuable book in my monster library (some 100 titles). This is the top secret knowledge, worth thousands and thousands of bucks. I really am not related to the author or publisher. Great stuff!

Found my first copy in the university book store in Ames, Iowa, and have been looking at it constantly, until I lost it in one of my numerous moves. Bassett has the right idea. Software should be **engineered**, not hand crafted, and Netron seems to have found at least one way to do it.

Another thing. To my knowledge, no one else in the field has advocated the notion of **balance** between source level changes and the re-use of executeable objects. This is probably the most important idea expressed here.

I thought I was becoming comfortable with OO until I ran into a group of Smalltalkers. What a mind bender! I learned things about OO that I didn't know. I also became concerned as, ostensibly for reuse purposes, the design stage decoupled logically unrelated functionality and fragmented real-world objects far beyond their natural granularity, to the point that I found myself mired in bitty components and methods with so little responsibility that I could no longer see the big picture. Worse, those myriad components now had complex interrelationships, most of which I could no longer see. I fully agreed that reuse was a worthy goal - but at the expense of readability and maintainability? Paul G. Bassett not only identifies and describes all of these issues (and much more), he has concrete solutions to these problems, with bottom line statistics to back up some pretty wild claims. His book is small - initially a concern for me. Don't worry. Paul G. Bassett is clear, concise, correct, complete. This, I strongly believe, is where we're headed.

I put this book on my "must have, don't loan it out," shelf right away.

I really like the approach and the presentation. The teaching style is casual and encouraging with a welcome absence of jargon. Don't get me wrong, if you follow the chapters you will get a FP site up and running, you just won't have to suffer a barrage of technical details to do it. Why utilize FrontPage in the first place if you are excited about the all the nuts and bolts of how web site programing works?

The included CD helps tremendously ... the combination of reading it and seeing the author go through the steps just further demystifies the process. Between the two presentations, you're bound to "get it." I watched some of the how to's, that I didn't even want to do yet. It got me interested and curious and gives you a sense of all the things you can do with FP2002.

I already had the FP Bible 2002 by this author. Did I "needed" the Virtual Classroom? ... Yes! The Bible is great for digging deep into the FP world, but the Virtual Classroom is clearly the right way to get yourself up to speed and in the running as a web site designer, painlessly. My advice, if you asked me, would be to get yourself a copy.

I found everything I needed in this book and the cd that comes with it. Having known nothing about FrontPage before owning this book now in just a couple of days I know a lot of things to create my perfect web site. Thanks David Karlins. You are one of a kind. I am looking forward to your other books to be published with the same format.

If you want to have an instant website without wasting a lot of time, this is the book for you. The CD takes you step by step to creat a fairly sophisticated website with input forms, scrolling/fly in text, differing themes, inserting pictures and video. etc. Using the CD, I really did not need the book all that much. Well worth it!!!

Text and multimedia combine in David Karlins' 384 page instructional reference guide, Frontpage 2002 Virtual Classroom to create an effective and "user friendly" learning experience. Readers will learn how to create large or small Web sites that are sophisticated and attractive, and effectively manage the organization, content, and style of their site. Readers can follow along on the CD-ROM as the on-screen guru explains and demonstrates the techniques discussed in the text. Frontpage 2002 Virtual Classroom is a confidently recommended "how to" introduction for all Frontpage 2002 users.

I am so glad I bought this book! It is truly a lifesaver! I learn better visually, so the CD Rom Virtual Classroom that's included helped me tremendously. Thanks to David Karlins' for sharing his knowledge of FrontPage. I hope to have my website up & running very soon!

I am an instructor for a 3D Game Content course and Game Art is one of our books. The industry art pipeline and procedures are very well laid-out in this book. Would love a second edition covering the next gen techniques that will be surfacing.

Great book that covers modeling techniques for game companies, uv layout's , future Tech Compontents such as Normal Maps, etc. A well good purchase for anyone who wants to know how it's done or to improve there knowledge.

I was an art director in the video game industry for a number of years and one of the most frustrating aspects was interviewing artists that wanted to be part of the industry but did not know how to prepare themselves. This book addresses that problem in a thoughtful and comprehensive way.

For any aspiring artist that wants to be in the video game industry, this is the book. The examples and explanations are clear and easy to follow. Using this book, you would be able to prepare a very capable portfolio.

Buy it, read it, and put the knowledge to use.

I have read this book and find it extremely informative. The book is written with the readers perspective in mind. It gives beautiful insight into the industry and the dynamics of it. It also has great walk-throughs with media on a CD that you can use as part of the "practical" experience.

Good Job!

People don't think alike. The person who can handle the programming complexity of doing a graphics engine is often not the person who is capable of designing the characters, scenery, and equipment needed for the rest of the game. In this area, the digital artist comes into his/her own. Note this says digital artist. This requires two separate skills, one is the ability to create vizualize what art is needed, the other is to use a computer rather than some other media to generate the desired image.

The game design business represents an opportunity for the digital artist to obtain jobs with real companies that are relatively well paying. This book gives an artist's perspective into the game industry. It talks about the industry, the work, and gives insight on how to get a job. But mostly it talks about what kind of art is needed for gaming. It shows the detail that is necessary to produce a visually pleasing game.

The CD included with the book includes numerous illustrations and files from Maya and ds max. It also includes a trial version of Rt/Shader software. The book presumes that you have a workingknowledge of at least one major 3D program (3ds max or Maya) and Photoshop.

This is a splendid book that is positioned to take an aspiring digital artist and carry him to the next level -- employment doing a job well beyond flipping burgers.

I like this book so much, I've purchased it 3 times! (My first copy was "borrowed" by one of my designer/producers, my second copy was left at Ubisoft SF, and this is my 3rd copy for myself.)

Great mixture of theories, old-school practices, and new-school techniques.

Although I personally disagree with some parts of what this book teaches, it this game design book is one of the most comprehensive I've seen. Well-recommended.

This might be a good book for teachers looking for material in their classes gamedesign or gamedevelopment. It may also be a good book for selfstudy, if you have the discipline to do the exercises. You need to have played a lot of the classic videogames though, otherwise you might not be able to do the exercises, which are mostly about thinking about gamedesigns and making little designs or design alterations on existing games.

Few people realize just how big a business digital gaming has become. Think of it this way: It's bigger than the domestic box office of the film industry. The amount of time spent playing games by young people now exceeds everything but television in time spent on entertainment. The main factor driving the development of the new extremely powerful computers is gaming, slower machines are capable of handling almost all office tasks.

The authors of this book have a great deal of experience in both designing games and teaching how to design games. This has given them an understanding of how beginning designers grasp the structured elements of games, common traps they fall into, and certain developmental exercises that help the student learn to make better games.

Note that this is not a programming manual, nor is it a graphics design manual. It is on game design. What are the characteristics that make a game, how can you prototype and play test the game without a horrendous programming expense, and finally some input on the game industry and how to decide on how you might like to be employeed in that industry.

I consider this an excellent book on game design. As an amatuer board game and basic computer game designer, I found a lot of the material extremely useful in the *process* of coming up with a game from start to finish.

The chapter on prototyping did a great job in showing how to go ahead and create a prototype from a game idea, while keeping it simple and concentrating on the "core gameplay mechanism."

The chapter on "Playtesting" and "Functionality, Completeness, and Balance" builds on the prototype chapter by emphasizing the iterative nature of design where one go aheads and evaluates, tries new things, identify problems and keep evolving.

The next chapter following is maybe the most important chapter that discusses whether you game is fun, goes in to some theory of what makes a game fun, and relates various techniques of improving player's choices so as to make the game fun.

This is a great book that gives you the necessary tools to go ahead and be able to at the very least create a viable prototype of a game that is possibly fun and playable.