{"id":25642,"date":"2020-03-17T08:34:00","date_gmt":"2020-03-17T13:34:00","guid":{"rendered":"https:\/\/www.hostgator.com\/blog\/?p=25642"},"modified":"2020-05-20T12:51:17","modified_gmt":"2020-05-20T17:51:17","slug":"books-every-software-engineer-should-read","status":"publish","type":"post","link":"https:\/\/www.hostgator.com\/blog\/books-every-software-engineer-should-read\/","title":{"rendered":"8 Best Software Engineering Books"},"content":{"rendered":"\n

This article is part of HostGator\u2019s Web Pros Series. In this series, we feature articles from our team of experts here at HostGator. Our Product Managers, Linux Administrators, Marketers, and Tech Support engineers share their best tips for getting the most out of your website. <\/em><\/p>\n\n\n\n

What do software engineers read in their free time? What should you read if you\u2019re interested in learning more about software development? <\/p>\n\n\n\n

HostGator asked, and I answered with my top picks for web developers and software engineers, people who\u2019d like to know more about programming, and anyone who has to work with cross-functional teams, negotiate a pay raise or convince people to follow your vision for a project.\u00a0<\/p>\n\n\n\n

Let\u2019s start with a classic introduction for people with a serious interest in software design.<\/p>\n\n\n\n

\"build<\/a><\/figure><\/div>\n\n\n\n

1. Object-Oriented Analysis and Design<\/h2>\n\n\n\n
\"Object<\/figure><\/div>\n\n\n\n

The number one book that I think most software engineers would recommend is Object Oriented Analysis and Design<\/strong><\/a>. It’s the big 'how do I architect?'\u009d guide, and it provides a lot of the background theory as to why you would do object-oriented programming, which is the major programming paradigm that is used currently. <\/p>\n\n\n\n

This book is a standard recommended read for anyone who\u2019s interested in software development<\/strong>. However, as a software engineer, you don’t want to focus solely on being good at writing software. <\/p>\n\n\n\n

You need to be good at that, of course. But you also want to figure out what other domains to build yourself up in because you’re going to need to communicate with people who aren’t technical. That leads to my next recommendation'\u00a6<\/p>\n\n\n\n

2. The Phoenix Project<\/h2>\n\n\n\n
\"The<\/figure><\/div>\n\n\n\n

As part of your work, you’re going to need to convince people who aren’t technical to consider your ideas<\/strong>. To make the best engineering decisions, it\u2019s important to have support outside of the engineering department. <\/p>\n\n\n\n

The Phoenix Project<\/strong><\/a> isn\u2019t a how-to guide. It’s a tech narrative about a fictional company that\u2019s transitioning to the DevOps model from an older, less integrated model of working. It\u2019s talking about the challenge of coordinating between operations and development, and how to bridge that gap and move forward quickly at scale. <\/p>\n\n\n\n

It’s a pretty easy read and a good book to help you get a feel for where you want to start becoming more cross-functional. You don’t have to become an operations expert, but it\u2019s a good idea to understand what operations is doing, so you can understand how your code is deployed beyond just, 'I wrote it and now somebody else has to figure out how to get this thing to work.'\u009d<\/p>\n\n\n\n

On the flipside, this book can also help people in operations and other departments understand what IT has to do to make the transition to this newer working model. The more different teams can understand each other, the more effectively they can work together.<\/strong><\/p>\n\n\n\n

Next, I recommend a couple of books that show engineers not only how to create new products quickly but also to decide if they\u2019re the right products to create. <\/p>\n\n\n\n

3 and 4. Lean UX and Sprint<\/h2>\n\n\n\n
\"Lean<\/figure><\/div>\n\n\n\n

Lean UX: Designing Great Products with Agile Teams<\/strong><\/a> is a great book, along with Sprint: How to Solve Big Problems and Test New Ideas in Just Five Days<\/strong><\/a>, for understanding how to build a product quickly and with low risk<\/strong>. <\/p>\n\n\n\n

This is important because you don’t want to write a program and then see if the market likes it. These books work together to give you a process and a philosophy to follow, to test early and to test often based on what the customer wants. These are also good books for people who work in other departments who want to learn more about how the development process works. <\/strong><\/p>\n\n\n\n

The four books above aren\u2019t new to me, but I\u2019m always looking to learn more. Here\u2019s what\u2019s on my list and why.<\/p>\n\n\n\n

5. Domain Modeling Made Functional<\/h2>\n\n\n\n
\"Domain<\/figure><\/div>\n\n\n\n

Right now, I’m rereading Domain Modeling Made Functional<\/strong><\/a>. This book looks at domain-driven design in the framework of a functional programming language, rather than a programming language that’s object-oriented. <\/p>\n\n\n\n

That\u2019s a different programming paradigm, and the book makes a compelling case as to why and where you\u2019d want to use a functional programming language-for example, when you need something customer-focused developed fast. <\/p>\n\n\n\n

6. Domain-Driven Design: Tackling Complexity in the Heart of Software<\/h2>\n\n\n\n
\"Domain-Driven<\/figure><\/div>\n\n\n\n

This book<\/strong><\/a> is on my to-read list because it\u2019s supposed to address how you translate processes into software. <\/p>\n\n\n\n

What does a process look like for somebody who doesn’t write software? How do you communicate about that process so you can translate it correctly into a software system? That requires communication among teams, maybe marketing, maybe sales in addition to engineering, to express those processes in terms of code. <\/p>\n\n\n\n

Books 5 and 6 are aimed at readers who are familiar with software engineering principles. The next two books I recommend are for anyone who ever has to work with other people-in other words, all of us.<\/p>\n\n\n\n

7. Never Split the Difference<\/h2>\n\n\n\n
\"Never<\/figure><\/div>\n\n\n\n

This book is about negotiation and effective communication with people with diverse opinions and perspectives. I recommend Never Split the Difference<\/strong><\/a> for just for anybody who\u2019s trying to do anything. <\/p>\n\n\n\n

For example, if you want to negotiate a better salary or make an argument for using a particular technology over another<\/strong>, this book is going to give you the tools to negotiate well. <\/p>\n\n\n\n

8. Pre-Suasion: A Revolutionary Way to Influence and Persuade<\/h2>\n\n\n\n
\"Pre-Suasion:<\/figure><\/div>\n\n\n\n

Pre-Suasion<\/strong><\/a> is one of those books that changes your perspective on the world. It focuses on how to set up situations so that you can be more persuasive in your discussions. When you read this book, it helps you see the world through the frame of persuasion, and you can see that things that you don’t think are persuasion can actually convince people to agree with your ideas. <\/p>\n\n\n\n

If you do any kind of marketing or negotiating<\/strong> with anybody, this book will give you the tools to be more persuasive even if you don\u2019t have a natural understanding of those skills. <\/p>\n\n\n\n

What Other Computer Engineering Resources Are Worth Reading and Watching?<\/h2>\n\n\n\n

Technology changes fast, and there\u2019s always something new to learn. Beyond books, I like to check out software conference talks on YouTube and see what looks interesting. <\/p>\n\n\n\n

Hacker News<\/a>, run by the startup incubator Y Combinator, is a great place to get the latest information from other users on things like programming, cybersecurity, 3D printing and other tech topics. It\u2019s a great resource for spotting emerging industry trends and deciding what you\u2019d like to learn about next. <\/p>\n\n\n\n

What\u2019s next on your to-learn list? <\/em><\/strong>Check out these HostGator blogs:<\/p>\n\n\n\n