Read more
CS Why is a book that presents a straightforward, curiosity-based approach to filling in the blanks around common, introductory material taught in Computer Science classes. If you have ever wondered "why is that?" about a programming phenomenon, historical tidbit, or common terminology, this book may have an answer that explains it.
Questions include:
Why do computers have trouble with floating point numbers?
Why is it called Bluetooth? Why does it use that symbol?
Why is it called bootstrapping?
Why don't modifications to function parameters persist once the function returns?
Why do we use the QWERTY keyboard?
... and many more.
Perfect for both students and IT professionals, this book provides the clear "why" to answer so many unstated CS questions. Take any example in the book, from base 2 to timezones, and you will have an answer that cements your insight on the "why" of the topic, reinforcing your rote memorization with deeper understanding and insight.
List of contents
Architecture History Infrastructure Networking and Security Programming
About the author
Rachael Little has a lifelong passion for computer technology and is currently finishing a PhD in Computer Science studies at the University of New Hampshire.
Christopher Little has a lifelong career in (and passion for) software and computer technology. He has been a developer and/or managerial at organizations such as NASA's Johnson Space Center, IBM, Health Language, BMC Software, and Gartner Group. He has started (and sold) several software companies.
Len Little has a dedicated interest in linguistics and computer security, and is currently getting an undergraduate degree in Computer Science and Cybersecurity at the University of Liverpool.
