“Yossef Gutfreund, a wrestling referee, saw the door begin to open and masked men with guns on the other side. He shouted a warning to his sleeping roommates and threw his weight against the door. Gutfreund's actions gave his roommate, weightlifting coach Tuvia Sokolovsky, enough time to smash a window and escape.

Wrestling coach Moshe Weinberg fought back against the intruders, who shot him through his cheek and then forced him to help them find more hostages. Weinberg lied to the kidnappers by telling them that the residents of the neighboring apartment were not Israelis. Wounded, Weinberg later again attacked the kidnappers, allowing one of his wrestlers to escape before himself being shot to death. Weightlifter Yossef Romano also attacked and wounded one of the intruders before being shot and killed.

The Germans offered an unlimited amount of money as well as the substitution of high-ranking Germans. The kidnappers refused both offers."

—Wikipedia on the Munich massacre. I'm reading about it in the wake of the attack on cricketers in Pakistan. Things could have been much worse.

permalink

My latest project: NewsFlash, a feed-reader with a flashcard interface

permalink

“If I get in five or six hours of writing, the other stuff [routine chores] feels satisfying, like a kind of grace. But if I have to do that stuff when I haven’t written—that’s a terrible thing."
—Jonathan Lethem_i   via

permalink

Alison L. Des Forges, Rwanda observer extraordinaire, RIP.

permalink

Resolutions

Most new years resolutions have failed by this point.

By definition, a new habit doesn't fit in with the mindset and lifestyle you currently have. You care about more than the resolution. You're really asking for the new mindset that enables it.

When you make a change its implications ripple through your life. For it to take hold, the rest of your life must make room for it. Reorganize, repack. Resolutions are simplistic. They encourage us to focus on one aspect of life, and to ignore implications for the rest.

Don't fix the action too quickly. Don't fixate on individual resolutions. You have somewhere to get to, and you must change in myriad ways to get there. Change requires practice. Make it a habit, a constant process of improvement. Keep sketching [1,2]. Iterate. What's so special about January first anyway?

paraphrasing myself from two years ago after reading TJ

permalink

Steampunk hackers and early adopters among the Amish

permalink

The superior civilization: Ants

comments

  
Kartik Agaram, 2010-03-18: E O Wilson, "Anthill": http://www.nybooks.com/articles/23763

permalink

I am thinking about the tragedy of the commons

We neglect what we collectively own.

More than a theory of economics, it is a cognitive phenomenon. Humans have trouble with small numbers. One millionth of this subway gets rounded down to zero. (This is one of the reasons gambling has allure.)

'Cognitive rounding' applies also to shared responsibility. This financial crisis has no single culprit because we all reacted to a situation, and by our reactions made it worse.

Kevin Kelly suggests we'll just go past ownership as an incentive. Is the free movement realistic in this expectation? I think it under-estimates human nature.

permalink

“The propensity to play is situated in very ancient regions of the brain. Rats that have had their neocortex removed still engage in normal play."
— Jaak Panksepp on the importance of unstructured play early in life

permalink

How to enter the Zone at will

You know what I'm talking about. Programming can be the best of times or the worst of times. Sometimes the fingers seem clumsy on the keyboard, tool after tool acts flaky, we scream and curse, we become aware of the huge tower of complexity we rely on. At other times all thought flies except for this one thing we're working on right now. The fingers fly, the thoughts hum, and we eventually exit the trance amazed at what we have accomplished, at how cool it all is. We call this the Zone, writers and artists call it the Muse, and it has taken a while to realize that it's just a mental state [1] only loosely influenced by external factors.

I too have chased after the Zone day after day for many years as I struggle to bring programming ideas to life. Like conversation, programming can give you anything but consistency. You never know if this session will be good or bad. Sometimes things are good from the moment you hit the keyboard. Most times, though, you struggle for a while before you find it, before you lose yourself. On most days it takes me 2 hours just to get going, to stop noticing the mechanical actions between thought and software. Since getting going takes so long I've gotten used to the idea that programming needs large quanta of time. I need my time to be divided up into chunks at least 4 hours long. The truly great sessions require 8 hour sessions, multiple of them broken up only by sleep without thought to external stimulus or time of day.

Or so I thought until now. A few days ago I noticed that I've gone months without hacking for 4 hours straight. My output is not reduced, indeed I'm accomplishing as much as I ever have. These days it seems I can make something out of even the stray hour that gets thrown my way. What changed?

What changed was that I started doing TDD. I started breaking big ideas down into lists of stories in a little text file, picking a story, writing test cases for it. That was it. Somehow, it seemed, just having stories and test cases served to focus the mind.

Did you ever find yourself thinking, "Man, for all the lengthy reasoning if I'd just heard about reason x I'd have been on board from the start?" Forget exercise-is-good-for-you, bruce-lee-beating-up-the-bad-guys, girls-like-it -- if I'd only known it would improve my posture I'd have started doing weights long ago. Forget politeness, a smooth ride, traffic safety -- if only I'd been reminded of speed limits and traffic cops and tickets, I'd have slowed right down.

And I would have been all over TDD if I'd known it would get me to the Zone at will. Forget all the lengthy rationales about project success rates, the agile manifesto, dealing with changing requirements, avoiding regressions. When I think about all those years of nursing my RSI, wondering what I was doing wrong after a lengthy disappointment, psyching myself up to the level of focus and discipline necessary for long hours at a stretch, procrastinating to avoid the grind, when I think about these things, oh man. If only I'd known.

(Inspired by this thread)

permalink