Reputation
1,297
Top tag
Next privilege 2,000 Rep.
Edit questions and answers
Badges
1 8 17
Newest
 Yearling
Impact
~25k people reached

  • 0 posts edited
  • 1 helpful flag
  • 163 votes cast
Apr
30
awarded  Yearling
Apr
21
awarded  Notable Question
Apr
7
comment C# Share Datatable in Multi-threading
-1 Just for the comment about smacking a developer
Apr
6
comment Why is referencing arrays, instead of copying them, bad?
Not necessarily true
Apr
4
comment Why is XML called a “language” exactly?
It doesn't describe anything, it doesn't interpret, it just is. So? Doesn't mean it isn't a language. This is a silly question.
Mar
14
comment Nested For Loops JavaScript
Nested for loops typically aren't expensive. But, of course, saying they're 'not expensive' is as subjective as saying they are. Depends what you're doing inside the loop, or what you're iterating over. In your case, it's fine.
Mar
7
comment What's the reasoning behind the “I” prefix naming convention for interfaces in .NET?
You know it's just naming convention. And if you suspect it's not, and it serves some functional purpose - google it. What kind of answer are you after? Pointless question.
Mar
3
awarded  Citizen Patrol
Feb
18
comment Should I throw an exception in case of a meaningful value outside of the range or handle it myself?
I tend to stay away from making assumptions about what the user 'meant' by passing particular parameter values, especially those my code doesn't cater for. Sounds like a similar case.
Feb
4
comment Report test failures “all at once”, or report them one by one
OP, there are two categories of testing (in this particular context). Their tests, and yours. If they haven't even attempted to resolve their bugs due to lack of testing strategy, that's piss poor business on their part. That said, your testing could be considered as user-acceptance testing. It's fine for you to test first, but don't feel any obligation to cater for the incompetency of a technical team of developers who are suppose to have already sorted it.
Jan
20
awarded  Quorum
Jan
20
comment How do I make up for a lack of feedback as a solo developer?
codereview.stackexchange.com - who says you can't get your code reviewed?
Jan
19
awarded  Popular Question
Jan
19
awarded  Nice Question
Jan
19
comment Specify optional parameter names even though not required?
I don't mind opinion, I asked for 'formal'. MSDN may be primarily opinion based, but it's formal enough for me.
Jan
19
comment Specify optional parameter names even though not required?
I hear what you're saying, but you've sort of missed the point of what I'm asking. Assuming a scenario whereby it is most appropriate to use optional parameters (these scenarios do exist), is it ok to name the parameters even though it's unnecessary?
Jan
19
comment Specify optional parameter names even though not required?
@MetaFight - good idea.
Jan
19
revised Specify optional parameter names even though not required?
added 176 characters in body
Jan
19
comment Specify optional parameter names even though not required?
I'd call the likes of the following article 'formal' enough for what I'm after: msdn.microsoft.com/en-gb/library/ff926074.aspx
Jan
19
asked Specify optional parameter names even though not required?