I've been getting into Ruby & other software engineering talks lately, as they complement my usual diet of quantum physics, neuroscience, and social psychology lectures. I'm not actually that smart, a lot of it goes over my head, but sometimes I get concepts and other times they prompt me to poke through Wolfram Alpha, Wikipedia, etc.
Anyway, Technical Talks:
- Here Be Dragons: Katrina Owen.
Starts off with some fun ranting about some bad code, then gets real. Fantastic.
- Sometimes a Controller is Just a Controller: Justin Searls.
How people on dev teams interact, and how to maintain sanity.
- API Design for Gem Authors: Emily Stolfo.
How to design your Ruby gem so people will actually want to use it.
- Don't Be a Hero: Sustainable Open Source: Lillie Chilen.
How to make sure your open source project doesn't die, and actually get other people to contribute.
Why estimation is important and how it goes wrong.
- Introduction to Introspection Features of Ruby: Koichi Sasada.
Gets into some of the low-level capabilities the Ruby engine gives you. I thought I knew a lot about Kernel and Object methods, but this taught me otherwise.
I guess most of these are "soft talks" in that they aren't about some new library or specific functions of programming. But these topics are critical to working on a team. Even if you know some or all the material, it's worth a refresher course now and again.