We started using Subversion at work shortly after I joined the team, so I thought I’d attend the “Subversion Worst Practices” talk. It’s billed by the speakers, Ben Collins-Sussman & Brian W. Fitzpatrick of Google (and of Subversion fame), as a light-hearted follow-up to the best practices session they held last year. I’m happy it will be light-hearted, because I wasn’t thrilled with the session last year, and didn’t feel I got much out of it.
They started out with the top 10 ways to sabotage your project with Subversion. It’s Friday, and there’s not that much to say about each of the slides, so I’ll merely enumerate the worst practices, without commentary, for now. Hopefully the slides will be posted later.
10. Argue about Version Control Systems
9. Do a Brute-Force Transition
8. Backups? What Backups?
7. Loads of Locales
6. Rule with an IRON FIST
5. Hide the Version Control
4. Use Complex Branching Schemes
3. Put Everything in the Repository
2. Use a Network Drive
(Oops, we do that…)
1. Really Clever Hook Scripts!
0. Edit the Repository Database
Obviously, this session was really a list of best practices presented in a humorous way, by pointing out the extreme case of not actually following those best practices.
I noticed the MacBook Pro Ben and Brian are using to drive their session has a bumper sticker on it: “My other computer is a data center.” I like it. It’s exactly what I’ve been doing to my computing.
It was nice that Ben and Brian left ample time for questions and answers. The audience appreciated the time to ask questions about how to apply Subversion best practices to their own repositories. Or just to bitch about some pain points. Fun stuff.