unclejamal

PODCASTS:
http://rubyrogues.com/ - about programming in general, not always Ruby-specific (below a list of some episodes I found good, among many others)
- http://rubyrogues.com/131-rr-how-to-learn/ - episode about learning
- http://rubyrogues.com/023-rr-book-club-smalltalk-best-practice-patterns-with-kent-beck/ - episode with Kent Beck
- http://rubyrogues.com/068-rr-book-club-growing-object-oriented-software-guided-by-tests/ - episode about the GOOS book

http://pragprog.com/podcasts - about programming in general
- includes interviews with UncleBob, Kent Beck, Ward Cunningham, etc...

http://www.functionalgeekery.com/ - about functional programming

unclejamal

Here's what I meant when I said tests can break even if you only move a method to a different class.

This was the code before we started refactoring:

class BreadShop { ...
public void deposit(int accountId, int creditAmount) {
        Account account = accountRepository.getAccount(accountId);
        if (account != null) {
            final int newBalance = account.deposit(creditAmount);
            events.newAccountBalance(accountId, newBalance);