Posts from April 2008
I just read this in Google Reader, and just starring it or sharing it seemed a very small thing to do. What I really wanted is to shout out of the window 'YES! THIS MAN GETS IT!'.
I was having dinner with a group of friends about a month ago, and one of them was talking about sitting with his four-year-old daughter watching a DVD. And in the middle of the movie, apropos nothing, she jumps up off the couch and runs around behind the screen. That seems like a cute moment. Maybe she's going back there to see if Dora is really back there or whatever. But that wasn't what she was doing. She started rooting around in the cables. And her dad said, "What you doing?" And she stuck her head out from behind the screen and said, "Looking for the mouse."
He calculates that a project like Wikipedia takes roughly 100 million work-hours to be realized. That's the amount of hours a US-sized population spends every weekend just watching ads.
I don't have a television - do I do anything productive with the time spent? Not much, but still, I click and type instead of zap.
At Resolver Systems, we practice Agile techniques such as Continuous Integration, Pair Programming, Iterations and more.
One fundamental rule of Agile Programming is that There should never be a broken trunk. This means that before checking in we must make sure that every test passes. This makes checking in a very expensive operation: 4 hours for a full test run in a single machine. In the meantime, you go on working on that tree, making things very difficult to keep track of, without some form of version control.
In this post I will investigate various Version Control Systems that can be run locally: Most of them are distributed, but I don't really care about it - I don't want to replace Subversion (yet). I just want to be able to check in every hour and have a local version history, before checking in to the central Subversion repository.