I did a quick streaming video today with the Separated Interface design pattern as our topic du jour. I wanted to see if the whiteboard would show up on video and if this was something people thought was valuable. It's certainly easy to pick a design pattern and talk about it fairly loosely with a few examples on the dry erase. It's a little shaky, so next time I'll try to keep the camera still and focused on the right thing.

The second installment is just a short introduction to two resources from Software Engineering Radio, a podcast I'm a big fan of that tackles issues in software architecture including languages, object systems, processes, patterns, etc. The first is an interview with one of the minds behind the Spring component framework, Juergen Hoeller, in which he talks about some strategies for managing large codebases. The second has the se-radio guys chatting about what components mean to a software architect, their main attributes, and conceptual design principles. Separated Interface is a key enabler in both topics when developing an object system.