Last night I did a short presentation on Scaling WordPress using WordPress.com as an example giving an overview of the solutions we use for different scaling issues as well as highlighting some solutions that you can try out on smaller sites:
Author: westi
Tybee Island Boat Trip
svn spelunking
As I sit here blaming code to find the original source of a line of code I’m beginning to think that svn needs a new improved version of blame called spelunk it would work something like this:
$ svn help spelunk
spelunk (curse, showup, show): Output the content of specified files or URLs with the original revision and author information in-line ignoring white space changes and following movement of code between files.
Yes – I know I am dreaming š
My ethos for sharing code
A recent discussion around the way we write and share small helper scripts inside Automattic made me think a lot about why I do things the way I do and why I am against “authorship attribution” in shared code.
The views I have are strong and I think a good guiding principle for working collaboratively with your peers especially in Open Source projects:
I am very strongly against authorship attribution ā it puts up a barrier to contribution by setting a subconscious ownership barrier around things.
I give you my code to do as you wish, I mold your code to do as I wish, I blame early and often when searching for bugs, and I expect you to have forgotten you wrote the tool Iām asking you about especially if you committed it yesterday!
What is your ethos and what do you think of mine?