Pete Smith shares from his experience, discussing what it means to fail and how to make the most of it
Dom Davis takes a look at the Impostor Syndrome, discussing how and why it affects developers of all sizes.
Martin Thompson talks about the characteristics of a good software engineer and explores the individual practices and techniques that can help bring out the engineer in everybody.
Dusty Burwell discusses about the negative effects of developing software and the potential problems it creates.
Kevlin Henney examines some examples of code that are interesting because of historical significance, profound concepts, impressive technique, exemplary style or just sheer geekiness.
Jason McCreary discusses how a number of books from The Reading List - Implementation Patterns, Refactoring, Design Patterns, The Pragmatic Programmer - helped him with becoming a software engineer.
Jim Christopher discusses the health problems developers may encounter during their long work hours sitting at a desk.
Laurent Bossavit provides some suggestions on how to bring the fun back into programming by developing new skills such as leprechaun hunting and brain debugging.
Rich Smith discusses the progressive approaches taken by the Etsy security team to provide security while not destroying the freedoms of the Etsy engineering culture that are loved so much.
Alison Lloyd examines some less-than-stellar occurrences in non-software fields, drawing out some ideas that she hopes will make software development a little less painful.
How Did We End up Here? 50:22
Trisha Gee and Todd Montgomery attack the technology industry’s sacred cows by exposing the motivations that hide behind them.
Pete Goodliffe keynotes on what it takes to become a better programmer, discussing tools for reviewing the personal skillset and techniques to help one “become a better programmer”.