Books like Beyond the Little Blue Box — picked by fans

The last time I reread a book was The Color Purple in college. This time, I revisited The Rise of Technosocialism.

I initially read it from a macroeconomic viewpoint. The second time was as a personal reflection. I saw my life differently after the second time. I was stuck between two black-and-white choices: go get a traditional job or accept entrepreneurial failure. 

The book revealed a third path, which is building in the gray zone. I can define my role in the growing digital economy without fitting into either conventional category. I now have a new perspective with new possibilities.

Rereading this book helped me see a flexible, innovative way forward beyond a traditional role and repeated setbacks. I am now embracing a more adaptable approach to my career.

This book changed how I think about money.

I used to think of non-cash (credit cards, PayPal, and crypto) as a vague construct that wasn’t real, unlike cash. Now I think of money as a system. I saw the difference between what I was taught about finance and how digital money moves. 

More importantly, this book forced me to think hard about resilience because my desmoid tumor, which I had fought for years and thought was gone, grew back. And I've spent years building a brand without getting paid. I wondered for four years what I was doing wrong. I now see navigating modern financial systems isn’t about knowledge but about resilience instead. I must adapt, be aware, and be resilient.

This book made me face my mindset around urgency and taking shortcuts.

I lost $10,000 in 2017 in crypto right after my father passed away, when I was in shock. I look back at how my emotions and the need to get rich quickly overrode logic. I now love the idea of getting rich quickly, not from likelihood or being practical, but from seeing it as humor. I saw how I can’t compress my learning curves without consequences. I learned a huge lesson in paying the $10K tuition for a lesson in security and diligence.

GRQ helped me reshape my perspective so I no longer look at that experience as a failure, but as a necessary step to building with clarity instead of chasing outcomes.

Often over the past few years, as a self-published author, I have felt invisible. But this book showed me what being invisible really is.

For me, this book is not just about immigration or labor. I can see how everything keeps running while leaving out the people who sustain the system. I thought I was outside the traditional system because with Bitcoin, I thought I was part of a rebellion and a new global movement.

I thought there was “the system” and then there was Bitcoin. I didn't realize Bitcoin is a system too. And I didn't see that some people have no system, and maybe never will. I started to be grateful to be part of something where I count, or at least have a chance to count.

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.

Okay, hear me out. Yes, this book was published in 2007. Yes, it’s ostensibly about ActionScript, the coding language in Flash, which no one uses anymore. But you won’t use this book to learn ActionScript or Flash: You’ll use it to learn how to make things move with code, in any language. You’ll skip over the ActionScript-specific parts in favor of the lucid explanations and helpful illustrations. Your visual brain will appreciate seeing how sines, cosines, and tangents are relevant—and necessary!—to make digital things move. (Your heart will wish your brain had paid better attention in trigonometry class years earlier, but hey, no regrets!) The chapters “Trigonometry for Animation” and “Velocity and Acceleration” alone are worth the purchase price.

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.

Michael Lopp, or Rands, as he is commonly known online, has been sharing his knowledge as a software manager for years, mainly through his blog. He is one of the most insightful voices about the art of management in a software environment, and even if you are not a manager yourself (and don’t want to become one), will make you understand and better collaborate with your own manager, and be ready when you need to lead a team or understand how it is to work with other humans.

When I first heard about cryptography at university, it sounded like mathematical magic. After looking into some randomly chosen crypto books, I was discouraged from digging deeper because they were full of math details.

Understanding Cryptography was different. It was aimed at engineering students like me, and it provided me with the most relevant facts necessary for designing secure devices. Since then, it has always been a great reference book for me.

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… show more.