The Worst Code — Michele Titolo

Every developer has been there--late at night, deadline looming, piling hacks on top of hacks to get a little closer to being finished, there are no tests, edge cases are totally forgotten. Many of us think these situations lead to the worst code we could possibly write. Under such conditions, it is difficult to write robust, well architected code--true--but this is not the only situation that leads to that end. Software development is a complex, creative process that can easily get out of hand. This is because one large factor is often forgotten about--the human factor. Avoiding writing the worst code ultimately comes down to how the people writing, spec'ing, testing, validating, and tracking the code interact.

This talk was presented at AltConf in June 2015.

Transcript

1. The Worst Code @MicheleTitolo
4. How To Create Software
5. How Not To Create Software
8. ❤ Devs
10. Soft Skills
11. Soft Skills
12. People
15. Work Groups and Teams in Organizations School of Industrial and Labor Relations, Cornell University
16. Teams
20. GOAL
21. GOAL
22. GOAL
23. GOAL
24. Team effectiveness
25. Team effectiveness
26. • coordination Team effectiveness
27. • coordination • collaboration Team effectiveness
28. • coordination • collaboration • communication Team effectiveness
29. coordination: activities required to manage interdependencies with the team workflow
30. cooperation: the willful contribution of personal efforts to the completion of interdependent jobs
31. communication: a means for enabling the more primary processes of coordination and cooperation
34. The New Science of Building Great Teams Harvard Business Review MIT Human Dynamics Laboratory
35. Effective Communication
40. Code Smells
41. Organizational Smells
42. team-within-a-team
46. I HAVE NO IDEA WHAT I AM DOING
47. central command
51. single points of failure are bad
53. isolation
59. unreachable goal
60. GOAL
61. GOAL
65. black sheep
70. Anti Patterns
71. Patterns
72. Processes and Attributes of Highly Effective Teams Graduate Programs in Personnel and Organizational Psychology, University of Waterloo
73. Thanks @MicheleTitolo
74. References Balsom, M., Barras, R., Michela, J., & Zdaniuk, A (2009). Processes and Attributes of Highly Effective Teams. Retrieved 6/10/2015 from https://uwaterloo.ca/psychology/sites/ca.psychology/files/ uploads/files/processesattributeseffectiveteams.jm_.v4.pdf Kozlowski, S. W. J. & Bell, B. F. (2001). Work groups and teams in organizations. Retrieved 6/10/2015, from Cornell University, ILR School site: http://digitalcommons.ilr.cornell.edu/articles/389/ Pentland, A (2012). The New Science of Building Great Teams. Harvard Business Review. Retrieved 6/10/2015, from https:// hbr.org/2012/04/the-new-science-of-building-great-teams Eckstein, J (2010). Agile Software Development with Distributed Teams. Dorset House.
75. Photo Credits • https://freepik.com • https://www.flickr.com/photos/8566600@N07/2101642994/ • https://www.flickr.com/photos/49782305@N02/7696681446/ • https://www.flickr.com/photos/13408725@N03/4952384268/ • https://www.flickr.com/photos/14993459@N08/3448832978/ • https://www.flickr.com/photos/9024682@N06/4112010372/ • https://www.flickr.com/photos/47595824@N00/2066474072/ • https://www.flickr.com/photos/112667526@N07/12189952184/ • https://www.flickr.com/photos/22412134@N06/3705540165/