Reputation
9,820
Top tag
Next privilege 10,000 Rep.
Access moderator tools
Badges
1 21 43
Newest
 Nice Answer
Impact
~504k people reached

May
5
revised Divide and Conquer algorithms – Why not split in more parts than two?
deleted 1 characters in body
May
5
answered Divide and Conquer algorithms – Why not split in more parts than two?
May
3
answered How can you prove an acyclic graph has n-1 edges?
Apr
29
answered How did they debug segmentation faults before protected memory?
Apr
25
answered Why do we need “callback functions”?
Apr
23
revised Approach to simplifying an algorithm
added 1739 characters in body
Apr
23
revised Approach to simplifying an algorithm
added 138 characters in body
Apr
23
comment Why do we need “callback functions”?
+ That's what callbacks are good for, but I hate having to write them :-)
Apr
23
answered Approach to simplifying an algorithm
Apr
22
revised How to calculate percentile in Java without using Library
added 344 characters in body
Apr
22
revised How to calculate percentile in Java without using Library
added 344 characters in body
Apr
22
answered How to calculate percentile in Java without using Library
Apr
16
awarded  Good Answer
Apr
16
comment Implicit optimization versus explicit optimization
+ Library routines should not be sluggards, but their main purpose is ease of use, correctness, and reliability. I discovered using LAPACK that it was actually not very efficient in the case of small matrices, but it still serves its purpose.
Apr
12
comment What to do when your colleagues don't value code maintainability
I saw things like that during my contracting days. It seems to me the real problem is the high turnover, and that is caused by a management style, starting from the top, that doesn't actually value its people. I could always tell, just by sizing up the CEO, whether this would be a good company to work for.
Apr
11
answered How meaningful is the Big-O time complexity of an algorithm?
Apr
9
awarded  Nice Answer
Apr
4
comment “Too object-oriented”
@ThuneGrill: Karl's right. Stick to pragmatic reasons, not religious ones. OOP is certainly a good idea, but I've seen it carried to ridiculous extremes. The result is making mountains out of molehills. Things that could be done in 1000 lines of code end up being 10,000 lines of code with classes galore. Then, Gee, it's hard to maintain, and the performance sucks. (No matter what collection classes get used.)
Apr
4
awarded  Civic Duty
Apr
2
comment Performance overhead of standard containers and boost
Here's what astounds me. The problem with all such recommendations is they are flying blind, like a plane in the clouds with no instruments. Just having wings and a motor won't get you where you want to go, without guidance. Sure it might be that new & delete are costly, but just avoiding those won't make the code fast. You need to know how to find out what to fix. Sure - profile - everybody says. They say it, but they don't do it, and it doesn't work very well anyway. Here's what works.