Also, what exactly do you mean by "parody"? I thought he was clearly poking fun at the world at large, but didn't get the sense that there was any particular other work which he was lampooning.
5,255 karma · joined May 21, 2009
http://www.maxcantor.net
my name is max cantor.
my email is firstname at firstnamelastname dot net
purveyor of vim cheat sheet posters
http://www.vimcheatsheet.com
Also, what exactly do you mean by "parody"? I thought he was clearly poking fun at the world at large, but didn't get the sense that there was any particular other work which he was lampooning.
If only everyone would just be quiet and follow my opinions about that...
From this, I take "hard work" to mean working mindfully, not "counting photographs" as in the article. To work and live mindfully is to do each thing as if you did nothing else: you are fully present in each moment, drinking in your surroundings without judgment or abstraction. A hundred trees are not a hundred trees--each one is a new experience, with different patterns in its bark and different rustling in its leaves. To use the article's example, a party is not a "party". To the "lucky" person, to the mindful person, they are not "at a party"; they are simply talking, laughing, connecting.
I strive for this kind of mindset, and grasp it sometimes. Like zen, the harder you try to hold on to it, the quicker it slips away. At least, I can always look at the trappings of my privileged middle-class life and know that, for these things, I am lucky, and that helps me stay mindful.
Considering the complementary term they use ("drains"), wouldn't it be more intuitive to call them "faucets" or "spouts"?
Just sayin'.
Url?
(Isn't version control mostly for text files?)
> If, while the upload's been happening, I've made more changes to my working copy...
(So you're uploading a large--presumably binary--file, and you're continuing to work on it while it's committing...)
> I have to carefully pick out my new changes and keep them separate from my old changes.
(Wait, what? In a binary file? Or did you commit the binary file and changes to smaller text files in the same changeset? If so, you should be committing them separately. Either you're making small commits to text files that commit almost instantly, or you're making large commits to binary files that you can't "pick out" changes from anyway. Gotta pick one.)
> As soon as the commit is published, other people may check it out and try building it...
> ... if I can't access the repository server – if it's gone down, or if I'm working remotely – then I can't commit at all.
> ... but there are many reports [weasel words] of it being somewhat prone to error. If your mergeinfo property has been corrupted somehow, it might be extremely hard to spot...
I see a lot of inconclusive beating around the bush here. The author doesn't want to come out and say that any of these are concrete showstoppers because they are all, at worst, edge cases that experienced svn users mostly know how to deal with anyway. Every VCS has its own bugbears like these, git included.
I have been using subversion for years; I do all kinds of insane nonsense with private branches, merging and merge-tracking, large asset commits and all of the things this article uses for its doomsaying. I run into big problems maybe two or three times a year.
The writer suggests that git is better.
For some reason, even though I have read numerous manuals and guides about git, and have grilled git experts, and have regularly used git myself, and presumably understand how it works, I have to go on a farcical journey into its implementation details every time I do ANYTHING. I always end up in #git, or calling a more git-savvy friend. Everyone inevitably has a different answer that involves a lot of shrugging and "Oh, I guess this actually happened." This was the result even when all I did was follow the instructions at help.github.com/forking, TO THE LETTER.
Perhaps I am just a moron, and subversion is just VCS for morons. If so, I am too far gone to realize.
In my completely non-expert opinion, tenure seems to be a multiplier. From a students' standpoint: A good teacher with tenure is a godsend, because they feel comfortable challenging the system to make sure their job (educating the kids) gets done. Conversely, a bad teacher with tenure is a cataclysm, because they don't really want to be there, the kids don't really want them to be there, and the school administration doesn't really want them to be there, but by God, they're staying, because it's easier to collect a paycheck and hate your job than change your situation. To use a metaphor from Kevin Smith's Clerks, tenured crappy teachers are perennially shitting their pants instead of lifting the lid on the toilet seat.
If not, can you feign ignorance of the definition and explain that you are thus literally incapable of providing an honest & informed answer; and since you are under oath, require a definition before answering?