Developer Books

Reviews Of Software Developers Books

Developer Books

Robert C. Martin Aka. “Uncle Bob”​


If you have not yet been recommended to read this book as an ambitious software developer, then it is about time. 

In his book, Robert, goes into depth on how to write understandable code which is self explanatory and does not require any redundant comments.

It highlights how you would solve several common convoluted coding scenarios by replacing it with extracted methods, limited arguments and clear intentions.

Learning how to write clean code will make you and your colleagues happy to read code written six months ago. No one has to rely on past knowledge of the classes and methods, because they are self explanatory

If you are going to read any book on this list, I would highly recommend that you started with Clean Code. 

Takeaway: Teaches you the mindset of how to write clean code.

Gernot S., Ralf D. M., Michael S., and Stefan Z.


Arc42 is a standard for how to document and structure all information surrounding the developement process and environment. 
The “Arc42 by example” is a brief by simple and practice case by case study of how other products and projects have implemented the Arc42 standard. 

The general guidelines for how to use the standard can be found publically available on their official  homepage as well as Github.

Eric F. & Co.


Design patterns can be boring and sometimes complex, but they are relevant for any software developer to know and understand. 

The “Head First”-series has made a great job of explaining design patterns in a simple manner. 

Through the use of practical scenarios and multiple illustrations on each page, they not only explain the concept of each design pattern, but also compares the patterns against each other. 

If you question why you should learn about design patterns, I would argue that it is an essential skill for knowing how to communicate you intend to another developer. 

Dev-to-dev chat: “I’ll be using a factory to create instances of the MVP”

Takeaway: Fundamental understanding of the most essential design patterns.

Joost V. & Co.


Some books are good on their own and some books are perhaps better because of the timing and context of the developers journey. Building Maintainable Software, it one of the later.

Although this book only looks at statistical code analysis form the perspective of the SIG’s (Software Improvement Group) code analysis tool, it can still bring some valuable questions and thoughts into the mindset of the developer if combined with Robert C. Martin’s “Clean Code”.

If you view “Clean Code” as the how and why you should write high quality code, then you should view “Building Maintainable Software” as the consequences and effectiveness writing low quality code can have on your system. 

Unmaintainable code kills programs and makes it impossible to repair. 

Additionally, if you project ever comes close to a mandatory SIG rating, you will, by reading this book, know what to do. 

Takeaway: Helps you understand why making large system with simple pieces of code is important.

Dawn G. & David G.


Similar to the “Head First: Design Patterns” book, the series of Head First books also covers Android development. 

If you are totally new to Android and want to get into the field of development, this is the book for you. 

Through its simple explanations and many illustrations, it manages to cover the foundation of Android development pretty well. 

I will mention that there will be a lot of repeated development steps in each chapter and it only gets worse the further into the book you get. However, if you are able to look past this (or skip past it), I still believe the book will be valuable as an Android 101. 

I should probably mention that they will expect you to know the basics of the Java programming language, as Android is based on Java. (did I mention they also wrote a “Head First: Java”?)

When you are finished with this book and you want to dive further into the topic of Android, you could start reading Reto Meier’s books and simple start developing and visit stack overflow when needed.

Takeaway: Fundamentals of Android development.

Joshua Bloch


Effective Java is intended for the more advance developers, who are already familiar with the fundamentals of the language.  

The book goes into both best practices within common scenarios (e.g. follow guidelines of equals and hashCode), as well as highlighting some of the narrower case, but highly valuable features of Java, which might have slipped past many developers in the release note (e.g. try-catch-with-resources or Generics versatility).  

The author, Joshua Bloch has been working as a software engineer at both Sun Microsystems (creator of the Java programming language) and Google. If you ever used the Math package or used the assert method, then you know some of his work already. 

Current I am in the process of writing an abridge version of the book, which eventually will be available on the skill building page.   

Takeaway: Teaches you the most effective ways of utilizing the java language based on performance, readability and compatibility.

Adam Tornhill


Your Code as a Crime Scene is essentially a book about utilization of version control systems (VCS) to analyze and determine hotspots in the codebase. Whether this is due to weird code couplings, high variations of authors on a single class, code complexity, or something entirely else, can be determined by using the source code analysis tool CodeMaat. A tool conveniently developed by the author, Adam Tornhill. The tool is demonstrated throughout the book and provides insight information about the state of the codebase.

It is worth noting that CodeMaat has, after the book’s publication, evolved from a command line utility, and into a full-blown code quality analysis webpage, with user friendly UI and storage plans. The new edition is called CodeScene and can be accessed for free on private or small-scale projects.

Takeaway: Analysis of a codebase’s code quality based on the VCS history.

Michael C. Feathers


“Working Effectively With Legacy Code” is a book for developers working in code bases, which has suffered from decades (perhaps less) of bad software practices. It highlights multiple common scenarios, which are often found in legacy code (e.g. monster methods, entangled code, untested classes), and comes up with a variety of approaches to solve the issue. Many of these approaches can also be found in other books (e.g. Single Responsibility Principle from Clean Code). However, regardless of this I found this book as well structured and written, and works good for looking up solution approaches after a first read. I will recommend the book for anyone working with a legacy code base.

Technology And Business Books

Dale Carnegie


Having difficulties with social interactions? Do you not connect with people easily?

Dale Carnegie’s book is over 70 years old and is still considered valuable today. This fact alone, should be enough for you to consider it. 

The book teaches the reader, ways of interacting with their surroundings in a way which will increase the likelihood of creating strong relationships. 

Does this sound sketchy? Sure. 

However, the reasoning of the books methods is based on basic human interaction patterns, which, regardless of your intend, will be valuable to be aware of. 

Takeaway: The two most important thing other people want to hear. Their own name, and themselves talking. 

Jeff Sutherland


SCRUM is a software development methodology, which any software developer today, sound at least have heard of. Maybe you are even working in an organization, which utilizes SCRUM.

Regardless, if you have experience with SCRUM, or whether you are new to the topic, Jeff Sutherland’s book will contain new and valuable details. 

In essence, SCRUM is about making the strongest foundation for a team to work and solve assignments. This is achieved through total knowledge transparency, cross functional teams, and short sprints with build-in product demonstrations and team retrospectives. 

Takeaway: Extensive knowledge of how the SCRUM methodology works and how it through the use of transparency and cross functional team, manages to outcompete the old fashioned waterfall methodology.

Timothy Ferriss


The 4-hour work week, is a different kind of self-development book. Normally, these types of books focus on some already established problem, like how to negotiate your salary, increasing productivity, or manage meeting better etc. 

However, in Tim Ferriss’ book, he takes all of that and questions everything established.

Why do you need to work from a local office, if you can do the same job from a computer on Bali. 

Why do you need to spend 37-40 hours a week to do a job, which you could finish in 10, if given freedom and the same amount of money in return? 

The book changes your mindset to think and act on the verge between cheating the system and outsmarting your surroundings.

There are so many valuable learning points in this book that I would recommend it to anybody feeling stuck in the 9-5 job.

Takeaway: Questions yourself why you are spending such a large part of your life stuck at a desk, when you, with the right motivation, could get the same done in less time, from any location in the world.

Nick Bilton


Hands down the best non-professional book I ever read. 

It tells the scary and true story of how the physics student, Ross Ulbricht, managed to start and scale the dark net drug market known as the “Silk Road” back in 2011. 

It follows multiple perspectives of the story. From how Ross earned billions by selling drugs online, to the FBI and DEA following his trail around the world. 

To me this story is so fascinating that I still do not understand how only a few people around the world knows about this guy. 

Next time you have an unscheduled weekend, read this book! 

Takeaway: A shocking realization of the scale of the darknets drug market

Kim Zetter


Countdown to zero days is an impressive piece of journalism work. It provides multiple detailed perspectives of the Stuxnet attack on Iran’s nuclear program back in 2012. Going into the field of global politics and software exploits.

I can best compare it to “American Kingpin” (my favorite book to date). However, countdown to zero days is suited for a much more narrow crowd, since it requires a high level of technical knowledge to understand the fundamentals of how Stuxnet worked.

Ashlee Vance


A view into the mind of the worlds currently most known entrepreneur. 

He may be a passionate and driven individual, but he is most certainly also a demand and difficult person to work with and for. 

Learning about Elon and his companies will give you an insight into how he views runs his businesses and why he is so successful at that. 

The story covers lows and highs and makes no excuses for the personal sacrifices which he is willing to make.

Takeaway: Inspiration and respect to the king of character it takes to make and manage companies like Tesla and SpaceX.


Hi, I'm the Author

My name is Daniel H. Jacobsen and I’m a dedicated and highly motivated software developer with a masters engineering degree within the field of ICT. 

I have through many years of constantly learning and adapting to new challenges, gained a well-rounded understanding of what it takes to stay up to date with new technologies, tools and utilities. 

The purpose of this blog is to share both my learnings and knowledge with other likeminded developers as well as illustrating how these topics can be taught in a different and alternative manner.

If you like the idea of that, I would encourage you to sign up for the newsletter.

Cheers! 🍺

Didn't Find What You Were Looking For?

Generic selectors
Exact matches only
Search in title
Search in content
Post Type Selectors
Scroll to Top
INTEGU - Cookie-consent

INTEGU uses cookies to personalize your experience and provide traceability for affiliate links. By using the website, you agree to these terms and conditions. To learn more see the privacy policy page.