Reddit reviews Joel on Software: And on Diverse and Occasionally Related Matters That Will Prove of Interest to Software Developers, Designers, and Managers, and to Those Who, Whether by Good Fortune or Ill Luck, Work with Them in Some Capacity

From software engineering, check out:

• Joel on Software (book, blog): a very approachable introduction to some of the challenges of writing software, deals with things like formal specifications, project estimates, and some unofficial "laws of software engineering".
  
  
• Mythical Man Month (book): probably widely known outside of software, this book is about software project management and is well-known for the anecdote of "adding engineers to a late project only makes it later".
  
  
• The Pragmatic Programmer (book): this is the defacto professional manual that many software developers read within their first few years of professional work. There is good mix of technical guidance and soft skills (working with a team, career development).

So this is what I would consider the "Core" reading list for anyone interested in programming games. None of this is really game specific though. These are just the fundamentals you need in order to be an effective Software Engineer.

Learn about...

C++ syntax: Programming: Principles and Practice Using C++ by Bjarne Stroustrup

Software Engineering: Code Complete by Steve McConnell

C++ gems: Effective C++ by Scott Meyer

Software Teams: The Mythical Man-Month by Frederick P. Brooks Jr.

Why we love Joel: Joel on Software by Joel Spolsky

Problem Solving: The Pragmatic Programmer by Andrew Hunt

Common Code Solutions: Head First Design Patterns by Eric Freeman

Pearls!: Programming Pearls by Jon Bentley

I'll do a supplemental on this in a few days that dives into specific topics related to engine development. All of this is generic enough that it will help you regardless of what you do. You'll notice that very little here is actually language specific. Almost all of this is about the art of making software and process of working with a team. These 8 books alone will make you think about making software in a whole new way.

1.) Treat your employees (every single one of them, no matter their position or seniority) with the same amount of respect. Most employees really want to be excited about coming to work, enjoy their job and have their contributions and ideas valued. Try to cultivate that type of environment. I'm not saying to bust out pizza parties and loosen the dress code, because I know work still needs to get done, but "work" and "fun" are not mutually exclusive.

2.) The managers that I've looked up to the most, are the ones who constantly ask: "What do you guys think?" I remember one specific manager at Hewlett Packard who took a very hands-off approach. (We had a good team there and honestly didnt need much managerial oversight because we rocked). Your employees are smart, they are in the trenches (so to speak) every day. Give them some autonomy over their own work and encourage them to work well together as a team.

3.) Find and read Bill Swanson's 25 Unwritten Rules of Management I've got an original copy of the spiral bound mini-book and its really good. Simple, straight to the point, pragmatic.

4.) Find and read Joel Spolsky's "Joel On Software"

5.) Don't make important decisions as a singular individual and then force them down onto the teams, especially in situations where employees might resent or actively fight (work around) the intended results. If you even see a hint of that happening, talk and work with your employees to find out what exactly they dont like, or think is a bad idea. Many times (as long as the conversation is positive and productive) you can find a better solution, find a way to minimize the negative impacts, or at the very least simply help your employees understand WHY the decision was made. Keep them on your side.

Joel on Software: And on Diverse and Occasionally Related Matters That Will Prove of Interest to Software Developers, Designers, and Managers, and to Those Who, Whether by Good Fortune or Ill Luck, Work with Them in Some Capacity : This book completely changed how I worked and why I worked.

Joel On Software.

You should also read The Best Software Writing, but those essays are all available online.

https://www.amazon.com/Joel-Software-Occasionally-Developers-Designers/dp/1590593898

One of the only "entertaining" technical reads I've ever had. Highly recommend, especially if you are somewhat new to the industry like I am.