Reputation
11,516
Top tag
Next privilege 15,000 Rep.
Protect questions
Badges
30 55
Newest
 Good Answer
Impact
~321k people reached

Jul
4
awarded  Good Answer
Jun
28
comment What's special about “non-blocking” node.js?
Node has a single-threaded runtime. You don't need locks if you don't have multiple threads. See, e.g., stackoverflow.com/questions/14795145/… for more info.
Jun
28
comment What's special about “non-blocking” node.js?
It's pretty easy to claim that there are no competing threads when there is only one thread.
Jun
12
awarded  Good Answer
Apr
9
awarded  Disciplined
Apr
5
awarded  Yearling
Jan
21
awarded  Nice Answer
Dec
22
awarded  Nice Answer
Nov
17
awarded  Necromancer
Sep
4
awarded  Good Answer
Sep
1
awarded  Nice Answer
Jul
21
awarded  Good Answer
Jun
17
awarded  Nice Answer
Apr
29
comment What is the benefit of git's two-stage commit process (staging)?
@Ian So part of the file changes infrequently and is shared and part of the file changes often, in incompatible ways, and isn't shared? Supporting this false connascence definitely sounds like an anti-feature.
Apr
19
awarded  Nice Answer
Apr
5
awarded  Yearling
Mar
7
awarded  Enlightened
Mar
7
awarded  Nice Answer
Sep
29
comment What is the benefit of git's two-stage commit process (staging)?
Ignoring local per-line changes and ensuring that your code differs from everyone else's in ways only you know about at the line level? That sounds like an anti-feature to me.
Sep
16
comment Should We Code for Performance or Stability?
In the end it comes down to two things: shipping software that end users can get value from; and changing that software over time in response to feedback so that it continues to provide value. We should be thinking about fitness, maintainability and performance in those terms.