3,714 reputation
11222
bio website
location
age 34
visits member for 4 years
seen Nov 25 at 17:20

Apr
3
awarded  Commentator
Apr
3
answered Development Teams - Can One Bad Apple Spoil the Bunch?
Apr
3
answered Do Programmers sometimes intentionally over complicate code?
Apr
3
comment How many developers before continuous integration becomes effective for us?
No, it's not typical.
Apr
1
comment What do you think was a poor design choice in Java?
Quite the opposite: Java should have a primitive complex double type. It sucks when doing complex number calculations.
Apr
1
comment What do you think was a poor design choice in Java?
@OP Returning NULL is a terrible way of reporting error conditions. If the caller doesn't check for NULL, they may or may not get hit by it, sometimes in a totally different place, and tracking it down to the source of error is often quite difficult. Return numerical error codes (that's different than returning NULL because they won't be treated as pointers) or throw exceptions, but do not return NULLs or NaNs.
Mar
13
comment In C++, is it a reflection of poor software design if objects are deleted manually?
Smart points do not guarantee exception safety either.
Jan
20
awarded  Teacher
Dec
28
awarded  Supporter
Feb
26
answered What are the things Java got right?
Feb
26
comment What are the things Java got right?
Checked exceptions are unpopular because they remind you constantly that you need to write exception-safe code, something people like to forget about.