epsilon = some very small number used in mathematical proofs, usually approaching zero.

OP is saying that this is too similar to cat pictures. I think that it is worlds better than cat pictures, but still not relevant to the HN community.

It took me a while to parse that statement as well. My thought on the appropriateness (or not) for HN was that it was a moderately disruptive way to produce what is likely a durable floor finish.

I'm not on a tear to get stuff like this killed, but I worry about how much stuff like it is out there if we let it in. It's getting close to imgur territory.

I had the thought it may not be relevant, but added it anyways. In the future, I'll filter what content I submit better. It's been a long day....

Thanks for the explanation.

Thanks; I went back and tried to remove some of the snippiness from my comment.

Thanks, appreciated and noted.

"The top two were robots, and number 3 were all the humans"

Not sure how you can love automatic programming but dismiss biology. Humans are an operating system that is not only time dependent, but spatial and gradient dependent self mutating automatic programming with asynchronous message passing that is also time/spatial/gradient dependent.

Oh yea, and inserting breakpoints and print statements not only take months, but also change your code in a case-by-case fashion.

It's like reverse engineering for masochists.

Nowhere in the video was it every implied that the doctor handed out antibiotics like candy. I wouldn't be surprised if this doctor actually wrote less antibiotic prescriptions than his younger peers.

Usually I write a little code, commit what it is supposed to do, then fixup all the little edge cases and bugs that come naturally. But what's important is that first commit is sets up a little problem with a clear goal, and then everything afterwards works toward that goal.

Two extremely useful aliases:

  [alias]

  fi = !sh -c 'git commit -m \"fixup! $(git log -1 --format='\\''%s'\\'' $@)\"' -    
                                                                                                             
  ri = rebase --interactive --autosquash

First alias allows me to create a commit prefixed with fixup! very easily. So workflow looks like this:

  2536aw3 implementing feature foo
  sfd93ja fixup! implementing feature foo
  ok4jzvd fixup! implementing feature foo
  k4okvxx fixup! implementing feature foo
  2okoswa fixup! implementing feature foo
  zxvorm3 fixup! implementing feature foo
  ko2koaa fixup! implementing feature foo

And then I rebase when git log --graph --pretty goes off the screen.

From my experience with super programmers:

The super programmer converts complex ideas into code coherent to the normal programmer.

The super programmer makes difficult decisions where the normal programmer sees only one option.

I was trying to find a clear description of what happened, with supporting evidence at the right times, and it was surprisingly hard (many arm-chair fencers).

This is the best I could find: http://shinalamandtheinfinitesadness.blogspot.com/2012/08/sh...

Another great GC discussion for LuaJit: http://wiki.luajit.org/New-Garbage-Collector

That's funny, I interpreted what he said a bit differently for "impatience" and "hubris". To me, impatience and hubris go hand in hand for a good hacker.

Impatience: Why is this code taking so long?

Hubris: I could write code that is way faster/better than this!

This is a bit of a tangent, but do you have any sources for consumer-grade desktop parts being lower quality than enterprise-grade? I'd like to read an in-depth hardware analysis that describes circuit board design, capacitor sourcing, etc.

I'm really curious to see how different equivalently priced ASUS and supermicro boards differ.

Read the comments here: http://news.ycombinator.com/item?id=4063592