Intive Blog

Books every dev should read

In intive-FDV there are many literature fans, so many, that there is a #literary channel in Slack where we share our favorite authors and titles. Some of us even attend reading workshops and interchange all we have read. But, generally speaking, both those who are passionate about this pleasure as well as those who are not that much, all know that learning is vital, to never stop learning. Because of that, besides being nourished from forums and events, we also take turns to give internal talks about different subjects every Friday afternoon, read articles, papers and technical books. Today we wanted to suggest a selection of the latter, the ones we believe are key for any developer.

  • Title: Clean Code: A Handbook of Agile Software Craftmanship

Author: Robert C. Martin

“The saying goes that a good programmer writes code that computers understand, but a good developer writes code humans can understand. The focus of this book is on teaching programmers the importance of writing legible code. It is oriented to the paradigm of Object Orientation: However, many of the principles put forward are functional for other type of paradigms. It is not a book focused on software architecture but on code legibility.” Rodolfo Cordero Sancho – DevOps.

  • Title: The Mythical Man-Month

Author: Fred Brooks

“Some people have called the book the “bible of software engineering”. I would agree with that in one respect: that is, everybody quotes it, some people read it, and a few people go by it.” Fred Brooks

“On this book many famous phrases come up, such as “Adding manpower to a late software project makes it later”). The author is an expert engineer, who worked managing important projects, like the operating system IBM OS/360 which took almost double the estimated time to be finished. This book sheds light on what normally fails in software development projects. We should bear in mind it was written in 1975, almost six years after NATO Software Engineering Conferences (1968-1969), where the tem Software Engineering is first coined. It is a highly recommendable book for project managers”. Rodolfo Cordero Sancho – DevOps.

  • Title: Peopleware: Productive Projects and Teams

Authors: Tom DeMarco and Timothy Lister

“In my opinion, it’s a real “head opener”. Back then, when I started the leader path, it made me see things in a whole different way than merely technically speaking. For that, it is based on a series of studies about the variables that affect the productivity of a worker in the knowledge era and the importance of the human role in development. It helps you understand how “peopleware” is more important than hardware and software”. Pablo Sanchez – Agile Coach

  • Title: No Silver Bullet – Essence and Accident in Software Engineering

Author: Fred Brooks

“It’s a paper about accidental complexity and essential complexity, an appreciation about complexity during the development stage. Roughly speaking, the first one is the complexity generated by the very developers while the other is the complexity itself. This paper is about how to minimize them and what the challenges for both complexities are.” – Rodolfo Cordero Sancho – DevOps

  • Title: Effective Java

Author: Joshua Bloch

“The book is a summary of good practices, well explained and with examples. On its third edition its content is up-to-date regarding features on newer Java versions. The author was a software engineer for Sun Microsystems and among other APIs, he was in charge of the design and implementation of Java Collections Framework.” Alejandro Gomez – Software Architect

  • Title: Design Patterns: Elements of Reusable Object-Oriented Software

Authors: Erich Gamma, Richard Helm, Ralph Johnson and John Vlissides

“Design patterns was a term created by Christopher Alexander, and architect specialized in urbanism”. He affirmed that simple and reusable solutions can be identified for common problems. There are many books about this topic, but this really comes out of the pack especially because of the patterns and the way they are described. It is focused on how to design a solution. It is the foundation to understand many frameworks and libraries, very handy if you want to create a framework or design an app from scratch.” Rodolfo Cordero Sancho – DevOps.

  • Title: The Hitchhiker’s Guide to the Galaxy

Author: Douglas Adams

“It is not a book about programming, but rather sci-fi classic literature. It helps you think out-of-the-box, with a twist of humor”. – Rodolfo Cordero Sancho – DevOps

  • Title: The Inmates are Running the Asylum

Author: Alan Cooper

“One more among “that kind of books” I like, those I call “head openers”. It has been translated into Spanish as “Technology Prisoners”, maybe due to what the extended title originally proposed: The Inmates Are Running the Asylum: Why High Tech Products Drive Us Crazy and How to Restore the Sanity”. Although the book has been around for over 30 years, it is still obligatory reference both for computing people and for movers and shakers from companies. It helps understand the product condition of software and for us to center on questions such as usability and interaction to deliver real value to users.” Pablo Sanchez – Agile Coach

We hope you liked this compilation of must-read books for developers. If you have an all time favorite, you can add it to the comments, to enrich this interchange further and further. Are you in?

Paula Becchetti

Paula is the editor of intive’s blog. She holds a degree in Audiovisual Communication from Universidad Nacional de San Martín (UNSAM) and is a Content Manager specialized in blogs, web content, email marketing and social media. Her extensive experience in the software industry makes her very valuable when it comes to translate technical content into a colloquial language. According to her own words: “I connect with the world through technology, but also through everything that breathes, sport, music and my travels.”

Add comment