I am Professor of Computer Science at Stony Brook University, and have spent the past thirty years thinking/teaching/writing about algorithms. Algorithms are the really cool thing about computer science, for they form the ideas behind any interesting computer program. And algorithms turn out to be the ideas behind many interesting aspects of life that have nothing to do with computers. I have written six books on algorithms, programming, gambling, and history –including the ranking of the historical significance of all the people in Wikipedia.
Knuth’s unique mix of playfulness and rigor came to define computer science as an intellectual discipline: computer science didn’t really have anything to do with computers, but everything to do with a particular way of seeing the world. Just browse and wonder at the beauty and precision achieved in these books.
Volume 3 (Sorting and Searching) is my personal favorite, and I encourage you to start there. During the pandemic, I finally got around to reading Volume 4A (Combinatorial Algorithms), which was published thirty plus years after Volume 3. It was the same feeling I had watching the movie The Phantom Menace years after growing up with the original Star Wars trilogy. I had forgotten just how unique and distinctive Knuth’s Art of Computer Programming is.
The bible of all fundamental algorithms and the work that taught many of today's software developers most of what they know about computer programming.
-Byte, September 1995
I can't begin to tell you how many pleasurable hours of study and recreation they have afforded me! I have pored over them in cars, restaurants, at work, at home... and even at a Little League game when my son wasn't in the line-up.
-Charles Long
If you think you're a really good programmer... read [Knuth's] Art of Computer Programming... You should definitely send me a resume if you can read the whole…
My life has been about programming for as long as I can remember. Learning to code was a way to connect with my dad and express my creativity at a young age. Since I grew up with code, it became the way I understood the world; often I could look at a process or program and immediately see its source code in my mind. I developed a very strong sense of aesthetics searching for “perfect code,” which for me was code that was not only error-free but resistant to errors. My studies, research, and career is about moving myself and all programmers closer to that goal: Software that never fails.
Continuing down the engineering part of this mini-curriculum, we have a collection of interesting ideas, each written by a different author, all of them inspiring.
Some of the chapters in this book I have reread more times than I can count, because the ideas are so original and intriguing that my fingers start to tingle.
How do the experts solve difficult problems in software development? In this unique and insightful book, leading computer scientists offer case studies that reveal how they found unusual, carefully designed solutions to high-profile projects. You will be able to look over the shoulder of major coding and design experts to see problems through their eyes. This is not simply another design patterns book, or another software engineering treatise on the right and wrong way to do things. The authors think aloud as they work through their project's architecture, the tradeoffs made in its construction, and when it was important to…
I was a humanistic psychotherapist first and came to astrology later and loved the way it didn’t pathologize and gave insight into our character and how that affects our destiny. I started to gather the charts of my psychotherapy clients (with their permission of course) and while not using this in their sessions, I was inspired by how they spoke their charts. Much of my understanding of how planetary positions and aspects manifest has been discovered by listening. I love how aspect patterns repeat through the generations within a family and what ramifications this has on the individuals. Who’s carrying the families karma?
This is another of my books held together with Sellotape.
A T-square is a particularly challenging aspect pattern within a natal chart and Tracy gives vivid descriptions of a variety of possible manifestations. This book will help us to see the positive and the negative outcomes available to us and potentially take more responsibility for the circumstances that befall us.
The author was the chief Silicon Valley writer for The Wall Street Journal during the first of the 1990s. He went on to become an acclaimed scholar in the history of science, engineering, and innovation. At the peak of his journalism career, the Boston Globe described Zachary as the most talented reporter on the Journal's staff. Zachary went on to write technology and innovation columns for The New York Times, Technology Review, and Spectrum magazine. Zachary has also taught courses on science and technology studies at Stanford University, UC Berkeley, and Arizona State University, where he was a professor from 2010-2020. He lives in northern California.
The software interface for Apple’s innovative Macintosh was largely (and legally) modeled on system software designed at the Palo Alto < California research center of Xerox, an East Coast photocopy company whose stodgy executives failed to realize the value of the coding breakthroughs they had funded and nurtured in the heart of northern California’s computer cauldron. Before anyone at the top of Xerox realized the enormity of their errors, the company had licensed to Steve Jobs and Apple key software technologies that animated the Macintosh revolution in the 1980s. Hiltzik’s richly detailed and readable history, based on scores of interviews, is the best account of the epic failure of an American corporate icon. Apple and Jobs went on to achieve glory while Xerox ultimately became a zombie company, having missed the greatest industrial wave of the past 75 years.
During the 1970s and 1980s, a number of brilliant computer eccentrics were thrown together by Xerox at the Xerox PARC centre in Palo Alto, California. These people created inventions such as the first personal computer, the graphic user interface, the mouse and one of the precursors of the Internet. However, the bosses at Xerox never really appreciated these men or their innovations, and accused them of just fooling around. Then along came the outsiders, such as Steve Jobs of Apple Computing, who left the PARC with ideas that they would later exploit and make vast fortunes on, propelling them to…
It was while on the job as an investment banker that I first heard about this new thing called Bitcoin, before the word "web3" entered the vernacular. Initially I was skeptical but curious. But I became convinced the underlying technology of blockchains was ushering in nothing short of a new internet. My father Don Tapscott and I agreed to collaborate on a major research initiative that became the international best-seller, Blockchain Revolution. Since then, I have traveled to 40 countries and seen first-hand how blockchain and now Web3 is changing the world, setting the stage for a new digital age. My new book charts a course for this coming transformation.
In The Innovators, Walter Isaacson reminds us that “innovation occurs when ripe seeds fall on fertile ground.” Like the earth beneath our feet, we stand on stratum upon stratum of technological innovation, each with unique markers of its age.
Sometimes, the right idea, person, or group of people arrives at the right time to sow the seeds of something new. Isaacson explores how this phenomenon, teaching us how the collaboration of many individuals working across time and space helped usher in the first digital age in a highly readable survey of the main players and events.
As we stand on the brink of a second digital age, we would do well to search our history for lessons before stepping into the future.
Following his blockbuster biography of Steve Jobs, The Innovatorsis Walter Isaacson's story of the people who created the computer and the Internet. It is destined to be the standard history of the digital revolution and a guide to how innovation really works.
What talents allowed certain inventors and entrepreneurs to turn their disruptive ideas into realities? What led to their creative leaps? Why did some succeed and others fail?
In his exciting saga, Isaacson begins with Ada Lovelace, Lord Byron's daughter, who pioneered computer programming in the 1840s. He then explores the fascinating personalities that created our current digital revolution,…
As a child of the microcomputer revolution in the late 1970s, I’ve always been fascinated by the concept of a general-purpose machine that I could control. The deep learning revolution of 2010 or so, followed most recently by the advent of large language models like ChatGPT, has completely altered the landscape. It is now difficult to interpret the behavior of these systems in a way that doesn’t argue for intelligence of some kind. I’m passionate about AI because, decades after the initial heady claims made in the 1950s, AI has reached a point where the lofty promise is genuinely beginning to be kept. And we’re just getting started.
Alan Turing’s 1936 paper “On Computable Numbers, with an Application to the Entscheidungsproblem” was foundational to the development of computer science. To this day, Turing machines, the theoretical computational devices imagined in Turing’s paper, are a research cornerstone as they embody the concept of “computable.” If a programming language can implement a Turing machine, then the language is deemed Turing complete and is, therefore, general-purpose enough to implement any algorithm.
Turing’s paper is readable, but Petzold’s book breaks it down in minute detail to explain the nomenclature and meaning behind Turing’s words. I believe all computer science students should study this paper, and you’ll be hard-pressed to find a more thorough review than the one presented in this book.
Programming Legend Charles Petzold unlocks the secrets of the extraordinary and prescient 1936 paper by Alan M. Turing
Mathematician Alan Turing invented an imaginary computer known as the Turing Machine; in an age before computers, he explored the concept of what it meant to be computable, creating the field of computability theory in the process, a foundation of present-day computer programming.
The book expands Turing's original 36-page paper with additional background chapters and extensive annotations; the author elaborates on and clarifies many of Turing's statements, making the original difficult-to-read document accessible to present day programmers, computer science majors, math geeks,…
I have been working with computers for decades now – having started with programmable handheld calculators and working my way up and down through mainframes, mini- and micro-computers. I always thought there is an art to writing software, and that good software can be read and admired. Maintainability, readability, and testability are some core needs for software, and after going through many programming paradigms, I feel that functional programming (FP) is the way to go – and several modern web frameworks agree. JavaScript (and now, TypeScript) are essential to web development, and I wanted to show how FP could be successfully used with those languages, and thus my book.
This book is essential in that it follows a systematic and scientific approach to software development, advocating for clarity in expressing algorithms, providing a rigorous framework for designing and reasoning about programs, and, fundamentally, always focusing on formal methods and mathematical techniques to ensure correctness and efficiency in programming code.
Most importantly, the book doesn’t just show you how to prove programs correct, but also teaches how to arrive from a definition to an efficient and correct solution, so I would recommend this to every developer.
I have been dreaming about Artificial Intelligence (AI) since a young age. I am currently Professor of AI at UNSW, Sydney. I was named by the Australian newspaper as one of the ”rock stars” of Australia’s digital revolution. Although this is highly improbable, I have spoken at the UN, and to heads of state, parliamentary bodies, company boards, and many others about AI and how it is impacting our lives. I've written three books about AI for a general audience that have been translated into a dozen different languages.
This is an entertaining and lighter read than my other recommendations about AI. It is specifically about chatbots trying to pass the Turing Test, and ultimately is a witty story of what it means to be human. For anyone who has ever mistaken an answerphone for a person, or a person for an answerphone!
A playful, profound book that is not only a testament to one man's efforts to be deemed more human than a computer, but also a rollicking exploration of what it means to be human in the first place.
“Terrific. ... Art and science meet an engaged mind and the friction produces real fire.” —The New Yorker
Each year, the AI community convenes to administer the famous (and famously controversial) Turing test, pitting sophisticated software programs against humans to determine if a computer can “think.” The machine that most often fools the judges wins the Most Human Computer Award. But there…
I’ve been a software architect for a very long time. I love hard problems, and I’m very passionate about collaborating with others to find the right solution to them. Software architecture is a challenging, multi-faceted discipline with very few resources to help you make the right decisions. That’s why I’m recommending these books on software architecture. These books helped me become a more effective software architect, and I hope they can help you become more effective as well.
Imagine sitting in a room with 50 of the top software architects in the world and have each of them tell you some brief words of advice about being a software architect.
Welcome to “97 Things Every Software Architect Should Know”. Each 2-page spread features a top software architect offering their advice on some aspect of software architecture. From technical skills to soft skills, this book has it all.
This book is a must-read if you are a software architect, or even thinking about becoming one.
I started programming in high school and wrote software in many domains for 30 years, from the early ARPA-net to massive credit card software. I wrote a FORTRAN compiler with one assistant in a year. I got hassled to do proper project management. Nightmare. It was all about inflated expectations instead of moving fast and winning. Then in 25 years of venture capital investing, I learned from many young companies how the little startups built quickly and well things that giants like Google literally could not get done. This book and my others spell out what I learned from the little guys who beat the giants.
Attending Harvard College gave me the opportunity to collaborate with great programmers in creating the early ARPA-net. But the best course I took was on compiler theory and construction, using an early draft of the material in this book.
Of course I learned how to build a compiler, which I did as my first job after graduating. But more important, I learned that a well-built compiler is a small amount of language-independent code with two major parts.
First the input part that realizes the content of the lexical and grammatical metadata, like today’s LEX and YACC, to turn the program being compiled into a semantic model.
Second the code generator that reads the semantic model and, based on generative model metadata, turns the semantics of the program being compiled to whatever form you want, whether executable code, assembler language, byte code or whatever.
This approach, while indispensable for compilers and…
