Reputation
4,108
Top tag
Next privilege 5,000 Rep.
Approve tag wiki edits
Badges
1 14 25
Newest
 Nice Answer
Impact
~167k people reached

Dec
28
awarded  Yearling
Dec
15
comment Higher coding standards for dynamic languages?
@miraculixx That's not confusion, that's deliberate conversion.
Nov
27
awarded  Good Answer
Nov
15
awarded  Quorum
Sep
26
awarded  Nice Answer
Aug
15
comment Asking back technical questions during the interview (as the interviewee)
@user61891 Why? It's a very reasonable answer. Don't fix what ain't broke.
Jul
31
comment Should java developers know about garbage collection algorithms?
Yes, they should. Otherwise they run the risk of writing software which breaks under heavy load.
Jul
17
comment How do you unit test private methods?
@Phil Complex object graphs are also a code smell.
Jun
13
comment Is there a point to writing in C or C++ instead of C# without knowing specifically what would make a program faster?
Performance is not the only reason one may choose C++ over C#.
Jun
12
comment How to convince management that I can lead a team?
Convince the team first.
Jun
8
awarded  Caucus
May
28
comment Does it make sense to write build scripts in C++?
@JarrodRoberson I used "scripts" too liberally. I mean its configuration files. I'm not sure if being declarative makes Maven automagically more portable and easier to maintain. It does make it less flexible though, which can be a pain in large projects.
May
28
comment Does it make sense to write build scripts in C++?
I liked SCons, it'a bit slow but very easy to use.
May
24
awarded  Nice Answer
May
22
answered Design: Calling back to the parent class
May
21
answered Why no fortran standard library?
May
21
comment Why I'm not selected in an interview?
I guess because you suck.
May
16
comment Commented short fancy code vs. uncommented longer easy-to-understand code - which is preferred?
@MichaelBorgwardt I wouldn't apply Kernighan's dictum blindly to every possible situation. The OPs example is a function written "as cleverly as possible" (or close to it) and yet it should be pretty easy to debug, if any debugging is needed. On the other hand, complicated bit-twiddling oneliners can be very clever, but will certainly be even harder to debug. (Also: Kernighan assumes that coding skills = debugging skills. It doesn't have to be the case. I've successfully debugged code I would not have been able to write.)
May
16
comment What would be the Impact of P=NP?
Of course the constant factors might be so large to make this just a theoretical problem... for some time.
May
16
comment Commented short fancy code vs. uncommented longer easy-to-understand code - which is preferred?
"The problem with the short version of the code, aside from it being more difficult for some programmers to read" -- any piece of code can be hard "for some programmers" to read. You just need to find stupid enough programmers. Don't dumb down the code to the lowest denominator.