On pairing:
- Recognize the power differential between knowledge gap
- Don't let someone type all the time.
- Don't pair on something that doesn't make sense
- Pair on stuff to raise the truck factor
"There's something so delightful about working in the secret dark while the world is asleep." Sandi on working in the early morning.
I wasn't a good enough designer to write code that was easily testable, and my tests sucked, so it was like a double whammie.
So let me redefine bad
(I didn't end up asking this question) How do you know when you're being too clever when you write your code?
"To me there's a fundamental divide in the way people think about objects. So that divide is where you're comfortable knowing the name of the class of the object or not. On one side of the divide, it's more important what it does than what its name is."
- Break things down into smaller pieces.
- When you have a mess it is often because someone reached for the wrong abstraction too soon. ^^ This fundamental tension drives OOP ^^
Wait until you have to, delay a decision. YAGNI. You'll never know less than you know right now.
You'll never know less than at 3:30 on Friday afternoon.
I have a deep sympathy for the person I used to be.
Incredibly practical code arrangement choices.