Heh, I think a far more egregious error is having the word "instance" appended redundantly in a method name. obj.SetUp() or obj.Setup() I'm indifferent to, but

Heh, I think a far more egregious error is having the word "instance" appended redundantly in a method name. obj.SetUp() or obj.Setup() I'm indifferent to, but (mostly) there's no additional info gained by appending "instance" to it. I say mostly because sometimes code could pass bound instance methods around for others to invoke alongside other functions.