Lawrence Lessig on "Free Culture"

http://www.oreillynet.com/pub/a/policy/2002/08/15/lessig.html

Code Complete Quote

"You might think of the lines between subsystems as being hoses with water running through them. If you want to reach in and pull out a subsystem, that subsytem is going to have some hoses attached to it. The more hoses you have to disconect and reconnect, the more wet you're going to get. You want to architect your system so that if you pull out a subsystem to use elsewhere, you won't many hoses to reconnect and those hoses will reconnect easily" -- Steve McConnell

"A class is a lot like an iceberg: 7/8 is under water, and you can see only the 1/8 that's above the surface" -- Steve McConnell

Inversion of Control Containers and the Dependency Injection pattern

http://www.martinfowler.com/articles/injection.html

"Manging at Microsoft" - A conversation with Microsoft Program Manager David Anderson

Nice method to move (push) the team to move forward,
to appreciate how the information is spread.

-----
SD: You've said before that developers shouldn't be measured individually. Why not? And how then does a manager recognize and reward the star players on a team?

DA: I'm not a believer in measuring individuals by their code production. Developing software is a team sport; it requires interaction and mutual support across the team. It's knowledge work and is best done in an environment of knowledge sharing. When you reward people for individual effort relative to their peers, you encourage them to hoard knowledge rather than share it. The manager should be measured by the productivity of the team, not the individual team members for their individual efforts. It's a system -- optimize for the system, not for the parts.

My style is to reward individuals for secondary contributions. I use the "language lawyer" concept from Fred Brooks (author of The Mythical Man Month). For example, I ask a team member to become our "lawyer," or expert, on unit testing and test-driven development, and I measure them by how much they learn and by how well they diffuse that knowledge across the rest of the team. I reward people to learn and share. It's behavior compatible with team success.

The Game of Amazons

El Juego de las Amazonas was invented in 1988 by Walter Zamkauskas of Argentina, and first published (in Spanish) in issue number 4 of the puzzle magazine El Acertijo in December of 1992.

The game description:
http://home.earthlink.net/~fomalhaut/amazons.html
or
http://www.cs.unimaas.nl/ICGA/games/amazons/

or very nice description:
http://jenslieberum.de/amazong/amazong.htm

Seems like a lot of fun (combination between chess, go, a little bit of "othelo")

Code Complete Quotes

"A software metaphor is more like a searchlight than a road map. It doesn't tell you where to find the answer, it tells you how to look for it." -- Steve McConnell

"When you look at the architecture, you should be pleased by how natural and easy the solution seems. It shouldn't look as if the problem and the architecture have been force together with duct tape"-- Steve McConnell