fr0sty

People use DVCS for its features and capabilities. Because it can do more things not because it is easier to use. In the case of git the 'simple' workflow runs into some troubles because git is designed to accommodate much more complex workflows and as a result some of the core concepts have been tweaked in what people consider to be 'unintuitive' ways.

People choose vi/emacs over notepad/ed/pico for many of the same reasons and people complain about many of the same things (it's unintuitive, complicated, confusing, and so on...)

Here's another crazy idea: don't run 'git checkout ...' on a dirty work tree. Problem solved.

Another one: don't reuse filenames as branch-names.

To be honest: I have the same problem with careless invocations of 'rm' ruining my day but when I'm muttering curses it is at my lazyness/stupidity and not at bash completions or the behavior of 'rm'

If you are having trouble with git losing your changes you shouldf really be committing more often. Once a change is in git it is very hard to lose but until it is in git losing it is very easy.

What is also missed is that most exchanges discontinued flash orders late in 2009. BATS and NASDAQ both discontinued the practice, Direct Edge still allows them (they are opt-in) and NYSE/ARCA never had them.

There is no way to send an 'exploratory' order as you describe and is is, as you suspect, impossible to cancel an order that has already been executed.

The only way the example in the article would be if there were no other available sellers at a price below 26.41 (in which case I'm curious why an algo would bother sounding starting at the low end instead of the high end. The only ways to get such a wide market would be for all the other sellers to have disappeared (in which case the buyer is not disadvantaged by the HF algo because he is getting his order done rather than not) or for the HT algo to have made a guess that other people would be willing to pay a higher price in the future for BRCM and bought all of the shares available up to and above 26.40 which is the definition of a short-term trading strategy and, I should also add, full of risk that the price that you just pushed .30 will fall back down without you having a chance to get out hence making it a losing trade.

Crazy, in this sense, perhaps equates more with 'irrational' than 'erratic'. In 08' Everyone basically knew why things were melting down (or had a narrative that fit the data) but people were pretty much dumbfounded at the massive move with little or no immediate cause.

Reg NMS does not allow a trade to happen outside the national Best Bid/Offer.

If the market is 99.99-100.00 you cannot trade even at 99.98

easy, and perhaps a bit naive. it is possible you may cause more market turmoil by halting only certain stocks which would push volume into ETFs, futures, options, and other stocks in the same sectors.

The markets are very interconnected and very fast moving. 'simple' solutions rarely work.

I think you are missing the thrust of Linus' point.

"... it's where everybody _has_ to write"

There is nothing wrong with an 'authoritative' repository to which everyone pushes. What is a problem for Linus, and many others, is when the authoritative repository is the _only_ repository and doing work locally or sharing work between users is impossible to do using the VCS tools and people resort to passing patches.

foo and bar are the Lorem Ipsum of code. They let you look at the flow without getting caught up in certain details. You look at 'for', 'while', 'if', and other operators more closely when the identifiers are place-holders.

The only thing shown unambiguously was that "that juice did not prevent scurvy". Taking this to reason inductively that "no citrus juice prevents scurvy" is the real problem. They discarded documented evidence and grasped at other straws instead of stepping back and investigating history.

If their record keeping had actually been so good they would have remembered that citrus (by whatever means, and not to the exclusion of other remedies) cures scurvy and would not have wandered off into the weeds chasing spoiled meat (which, if the navies were at sea for years at a time could not possibly have been the case).

I don't see the 'direct progress' you mention, then again maybe my sarcasm detector is miss-calibrated.

Try doing the same with seven people + luggage in a ford van (1.8l diesel). It is surreal to be driving 140kph and be passed as if you were standing still.

BTW, if you want a nerve-wracking experience try driving the same setup in Italy.

freecycle them. There are groups in most population centers. Someone out there begging to find that tivo console cable.

Me and my wife have been getting rid of items not valuable enough to sell but too valuable to pitch through that channel for a while now.

What was the original article? I can't seem to hunt it down.

You can change your mind and turn a 'bookmark' into a 'branch' and back again. you can also fold your branch into another one and pretend it never happened. Or you can pick your branch up and place it somewhere else in the tree, or...

GIT_EXTERNAL_DIFF lets you use emacs as your diff tool.

http://stackoverflow.com/questions/255202/how-do-i-view-git-...

I know the 'wow' factor is greatly lessened but I wonder if two sets of in-ear headphones wouldn't solve this problem easily. 20dB+ of noise isolation is not uncommon and the addition of bluetooth (or even a physical tether) to pipe sound between people would make conversation simple.

If I could get over the feeling that it would look incredibly out of place at a bar or restaurant I would pursue the matter further.

If you require more than a day to recover you should either be doing less strenuous exercise or you should be lowering your number of workouts per week.

I used to sit next to a 100+ mile/wk runner and he ate nothing out of the ordinary, just more of it (100miles of running is a 10-14k net calorie increase, depending on who you believe).

In defense of the GP: he probably did not mean 'travel through an intersection after slowing only slightly, or slowing at all'.

The increase in perceptive capacity between slowing to 2-3 ft/sec. vs coming to a complete stop is negligible (and allows one to stop completely if the situation warrants it).

You didn't notice I right justified then. My peeve with embedded tabs is they are editor-defined and generally too wide.

    i       = 0.0;
    Tomato  vs.     Tomahto
    Integer vs. Doubles
    Integrals       vs.     Derivatives

> ugh, syntax highlighting

Care to explain? I didn't know there was debate on this point.

    Tomato  vs. Tomahto
    Bug     vs. Feature
    Tabs    vs.  Spaces

Either approach introduces about as many problems as it solves. I personally like being able to line things up with a few extra spaces to give some hints to my future self regarding the structure of my code.

Live preview falls short in many ways:

Visual lag: there is always some lag, and blurring if motion is involved with an LCD display. Action shots are just a guessing game.

Loss of resolution: The human eye can resolve detail a lot better than a small display. This is especially important for getting accurate focus.

There are other factors as well.

Alternatively:

"Oh no, I'm trying to paste this block of text from an email and it thinks every line is a new paragraph!"

Besides, Markdown was designed to be readable as plaintext and test written with the expectation that single return -> linebreak is not easily readable (unless people are in the habit of indenting the first line of their paragraphs.