Programming is a wonderful profession for problem solvers, and a random sampling of developers will generally have different ways of solving the exact same problem. This can be great in teams, as it allows finding solutions that resolve the unstated issues: performance, flexibility, and maintainability being some of the more frequent. But programmers tend to also have egos, and think their way is the correct way, disregarding one or more facets of a problem, and this is when we have conflict within our profession. How can we resolve those conflicts? And when does quantity of code give way to quality of code — and how do we even judge quality? We'll discuss these issues, some potential ways to resolve them, and how we can become both better programmers as well as communicators.


Comments are closed.

TJ Draper at 14:18 on 7 Feb 2020

Good reminders. Always need to hear about how we can improve code quality, reach out to peers, don't work in a bubble, work on our craft. Don't get stuck at expert beginner.

ROBERT A GADON at 14:20 on 7 Feb 2020

Thank you Matthew for your inspiring and enjoyable talk.

Inspiring reminders that we always strive to continue learning and improving.

Fantastic talk Matthew! Good pace, great points made, and good inclusion of the community.

Good insight and analogies presented.

Dana Luther at 08:52 on 8 Feb 2020

This was a great talk. The concept of twos really resonated with me, so I love that subtitle change. It’s made me start thinking about my own skill trees and where I may need to challenge myself to figure out where I need to start asking new questions to grow further.

This talk really resonated and challenged me to keep progressing in not only mastery but collaboration and communication.