urschrei

http://bikes.oobrien.com/newyork/ is a bit more comprehensive.

I would regard being referred to as a "feminist bitch" (or feminist anything, for that matter) as a point of pride.

There is: http://stackoverflow.com/questions/4806448/how-do-i-install-...

I agree, but that's more of an information design problem; adding an explanation of the RFC 2119 key words (or rather, the facility to provide a clear, concise explanation) would be an interesting next step, along with the ability to remove things like ASCII art. Anything beyond that is well into the realm of textual editing, and I suspect that there would be a lot of crying foul, considering that one of the main aims of these RFCs is to avoid ambiguity and the need for interpretation (certainly beyond narrow, well-defined circumstances) – never mind that as you point out, specs are never implemented "correctly".

Something like Github's "forking with the edit button"[1] functionality would be perfect for this. If you want to make a correction, press a button to see the content you were looking at in a web-based editor. Make your changes, and add your email address to a notification field. Changes go into an approval queue, and you get an email if/when your change goes live. No need to expose the casual user to the perils of DVCS, though of course a "proper" git-based infrastructure would exist in parallel for people who want more control.

[1] https://github.com/blog/844-forking-with-the-edit-button

The moral of any story involving SVN is: "Switch from SVN".

"Jumped the shark" posts are an antipattern.

You attempt to explain partial function application and currying on page 1. Using opaque examples.

This makes no sense; people who have experience with FP concepts don't need to know that, and those who don't won't be able to understand what you're talking about. Saying things like "I promise, this will get easier over time" isn't actually helpful.

Also, the text is low-contrast and difficult to read.

I can't speak for anyone else, but I would personally be extremely hesitant about taking a job anywhere that doesn't use a DVCS (and, realistically, for 'DVCS' read: Git or Hg). The technology an organisation uses says a lot about its culture. Anyone who hasn't switched to, or isn't in the process of switching to a DVCS is at a huge disadvantage.

Well, OK, but the answer also addresses other cases such as function/method decoration, passing arguments to the decorator itself, and passing arbitrary arguments. I agree that it's a little verbose, and the excessive comments and examples do detract from the clarity of the answer a little, but it's an excellent answer, nevertheless, if only because it leaves no use cases unexplored (excepting class decoration, but that's sufficiently orthogonal, I feel).

Your answer isn't wrong, but as an exercise in pedagogy (which is the point of SO, or at least one of its major aims) it leaves a lot to be desired, and wouldn't garner many upvotes. Not everyone understands what the term "syntax sugar" (and really, shouldn't that be 'syntactic sugar'?) means.

he did with one billion dollars worth of pressure on him The amount of money at stake is not an excuse. Sorry.

[…] and are willing to do whatever is necessary to make it go away. It's not going to go away, and he and ABnB have massively compounded the problem by wanting to "make it go away", instead of dealing with it in a humane and sensitive manner.

Yes, you are; SVN doesn't allow you to commit parts of a file -- it works at the file level. Git allows you to commit an arbitrary subset of changed lines from whatever files you've changed in your working copy. It doesn't track changes to files, it tracks changes to content in its tree. See here for a more complete explanation: https://git.wiki.kernel.org/index.php/GitFaq#Why_is_.22git_c...

I would respectfully allow that anyone who can't comprehend what the index is for with the aid of two paragraphs and a diagram should be looking for an alternate career. The index is important. It's one of the great things about Git; without it, you wouldn't be able to create commits from a subset of the difference between your working directory and HEAD. It also has a confusing name, but here we are.

What exactly do you mean by Java-in-Python code? Do you have examples? I find that code written using Pythonic idioms gets a high Pylint score, without having the slightest whiff of Java about it. That's not to say that its defaults aren't excessively fussy in some cases, but it's easy to tweak so that it doesn't whine about too many public methods or using magic &c.

The linked article is seven years old. For more up-to-date Python TDD techniques, see chapters 13 & 14 of Mark Pilgrim's 'Dive Into Python' (available free at http://diveintopython.org/), and for Python 3 (though plenty applies to Python 2) chapter 9 of 'Dive Into Python 3' (available free at http://diveintopython3.org/)