Adam Tornhill on Good Engineering Culture, Technical Debt and Ways to Reduce Inter-Team Conflict

Published: May 15, 2017, midnight

This is the Engineering Culture Podcast, from the people behind InfoQ.com and the QCon conferences.\n\nIn this podcast Shane Hastie, InfoQ Lead Editor for Culture & Methods, spoke Adam Tornhill of Empear on combining psychology and software engineering, technical debt.\n\nWhy listen to this podcast:\n\n - The problems in software engineering are not technical they are almost always people related\n - A lot of technical debt is not actually technical in nature \u2013 it is due to organisational and social factors\n - Research that shows that the number of developers who work on a block of code is a predictor of the number of quality issues that code will have\n - There is a cuttoff point above which adding more people to work on a codebase becomes a negative return is fairly low\n - Safety to be able to admit to not knowing, collaboration and constant learning are key to a healthy engineering culture\n - Complex areas of a codebase which change frequently are the best targets for technical debt reduction - hotspotsInter-team conflict is inevitable unless you have an engineering culture where there is a clear and compelling common goal\n\nMore on this: Quick scan our curated show notes on InfoQ http://bit.ly/2qkQtsj\n\nYou can also subscribe to the InfoQ newsletter to receive weekly updates on the hottest topics from professional software development. bit.ly/24x3IVq\n\nSubscribe: www.youtube.com/infoq\nLike InfoQ on Facebook: bit.ly/2jmlyG8\nFollow on Twitter: twitter.com/InfoQ\nFollow on LinkedIn: www.linkedin.com/company/infoq\nWant to see extented shownotes? Check the landing page on InfoQ: http://bit.ly/2qkQtsj