lucastheisen

what is a reasonable walking distance? 9% seems like a surprisingly small number.

Anyone seeing significant performance impact with CSP? We simply enabled an extremely lax policy on a Jira service desk instance and are seeing a 15-30% performance cost loading the summary page. Also, has anyone else come up with a consistent way (short of watching browser timeline) to determine the performance cost?

I find it useful to differentiate bug from feature because they have a very different information set associated with them. Bugs need to provide description, steps to reproduce, expectation, observation, workaround and are require a write up as part of their completion (root cause). Features, on the other hand, need only a requirements list.

Relevant: http://www.cc.com/video-clips/h71t46/drunk-history-jack-pars...

Talking over the phone doesn't show me the code/command/text we are talking about. It takes far more words to "talk" through a problem than it does to show the source...

I haven't tried the os feature version, but I assume it is the same one you can install from chocolatey... If so, then yes, it has ssh-agent.

I have as yet been unable to get the code completion working. Were you able to?

Any chance you could add nerdtree like behavior for the directory tree? I sooooooo hate reaching for the mouse.

I love how it was more acceptable for your general to be drinking vodka by the glass full than it would have been to drink the "American Imperialist" drink.

Im not sure how a signature could prove who signed it. Handwriting analysis can tell some things, but how many people still sign enough of a name to actually analyze. Look at the [Jack Lew signature](http://www.google.com/imgres?imgurl=http://images.politico.c...), assume that doesn't tell anyone much about _who_ signed it.

Funny you mention "as long as I can type". Recently had back surgery which makes it difficult to sit, hence difficult to code. Got me to thinking about all the things that could cause me to stop coding... Loss of ability to type (fingers/hands lost). Loss of eyesight (though in college we had a blind developer). Inability to sit (back problems). Loss of mind (dimensia/Alzheimers). Loss of motor control (Parkinsons/paralysis). Im sure theirs more, but like you, i imagine I will be doing this until i cant...

This is a perfect bug report. Humor, steps to reproduce, a real world problem... This would be a bug I chose to work on as soon as possible (if it turns out it is something that can be fixed in this project alone).

is that really more work than:

  int res;
  try { res = Integer.parseInt( s ); } // if part
  catch ( NumberFormatException nfe ) { } // else part

The words are different (try/catch instead of if/else), but still 2 blocks of code with similar syntax...

If you are using 'set -o vi', then you can just use 'ESC' -> '/<somePartOfCommand>' then use 'n' to iterate in reverse order through the commands that match the vi regex. really powerful and useful.

that was a good chuckle... thanks for sharing.

No matter how much effort and thought is put into writing quality code, looking back in a year or two I will cringe at it. Second, I recently saw the accepted answers per tag on broken down by average age on stackoverflow. Just realized I am over the hill (as far as software development goes)...

Agreed... On my second year of $12 and happy as day one.

I don't have anything to add, but thank you for the story.