Reputation
432
Next privilege 500 Rep.
Access review queues
Badges
5 13
Impact
~121k people reached

Jun
23
comment Should I give the answer to a failed interview coding exercise?
@André link updated.
Jun
23
revised Should I give the answer to a failed interview coding exercise?
Fixed blog link.
Jun
17
awarded  Popular Question
Apr
11
comment When should you call yourself a senior developer?
@Pithikos Can you provide a link or name of a study or an article?
Jul
9
awarded  Good Answer
Jan
8
awarded  Nice Answer
Dec
3
comment Leading an offshore team
It would have been much more difficult to be successful. I was handed a group of developers without the opportunity to vet them. Out of the 8 developers, 2 or 3 could work independently.
Sep
30
awarded  Necromancer
Aug
16
revised When should you call yourself a senior developer?
deleted 15 characters in body
May
13
comment Is this a Best Practice with Enum in C#
By the time you've got a number of switch statements it's too risky to change the switch statements (there is something to be said for working code, testable or not). If the application is not a proof of concept (POF) or not a throw away application us an object hierarchy.
May
13
comment Is this a Best Practice with Enum in C#
+1 I don't know why you got downvoted. It's a reasonable answer.
May
13
comment Is this a Best Practice with Enum in C#
+1 I don't know why you got downvoted. It's a reasonable answer.
May
13
comment Is this a Best Practice with Enum in C#
@Katana314 Nicely done. I agree with your approach. Too often I have seen methods such as reassignTask that contain massive switch statements or if/else that evaluate every permutation of an enum.
Feb
18
awarded  Caucus
Jan
22
revised My boss has a bad case of “Not Invented Here”
edited body
Jan
22
revised My boss has a bad case of “Not Invented Here”
edited body
Jan
22
revised My boss has a bad case of “Not Invented Here”
deleted 60 characters in body
Jan
22
answered My boss has a bad case of “Not Invented Here”
Jan
11
awarded  Popular Question
Dec
31
comment Would it be better to have extra checks, or would it be a waste of time?
+1 Nice analogy! But I disagree. By adding a conditional check, you might have just covered up a bug (or blind spot in the analogy's case). Keep it simple, if it's not needed then don't code it. Adding code for possible future cases or coders is a form of future proofing. By writing simple code, you are enabling future coders easily grok your code.