Reputation
1,888
Top tag
Next privilege 2,000 Rep.
Edit questions and answers
Badges
13 25
Newest
 Revival
Impact
~47k people reached

May
15
comment Naming functions that retrieve a value
-1 We know some people do this, but you are not making a case. Is this a good idea? Why? Particularly, I don't think it is, because the resulting names are confusing. Does "Celsius" get the quantity in Celsius, set it, compute it...?
Feb
25
awarded  Caucus
Feb
25
awarded  Constituent
Feb
18
comment When do you use a class instead of a record when you do not want to use mutable fields?
@fairflow: According to this stackoverflow.com/questions/5858550/f-records-vs-net-struct, F# records are actually reference types, so I guess value types are of no use to you here.
Feb
9
awarded  Taxonomist
Jan
20
awarded  Citizen Patrol
Jan
20
answered When do you use a class instead of a record when you do not want to use mutable fields?
Jan
3
comment What is Developer Anarchy?
What a lovely buzzword!
Nov
27
answered How to choose a development method?
Nov
7
comment Validation and Verification explanation (Boehm) - I cannot understand its point
@Andrew: I know, I know... That's why an ontology study group has just been set up within ISO JTC1 SC7! Things are far from perfect. :-)
Nov
4
answered Validation and Verification explanation (Boehm) - I cannot understand its point
Oct
26
comment How do we know to favour composition over generalisation is always the right choice?
Ever heard of semantics?
Oct
11
awarded  Yearling
Oct
10
comment how to convince manager to allow stack overflow
Is Dlbert your middle name? ;-)
Oct
5
awarded  Notable Question
Sep
5
revised Choosing the right version control system for .NET projects
added 87 characters in body
Sep
5
answered Choosing the right version control system for .NET projects
Sep
1
comment Should a project start with the client or the server?
@Oded: +1 That should be an answer rather than a comment.
Aug
17
comment Sporadic unittests or TDD?
@jimmy_keen: Sorry, but I am not convinced. Basing your testing strategy on the perceived likelihood of the code failing makes no sense. Precisely, defects (i.e. bugs) are about unforeseen circumstances, and testing tries to create those circumstances so that defects manifest as failures and are thus detected. You cannot assess the likelihood of a piece of code failing, not even close. Unless you perform some kind of formal proving, which I imagine it's not in the OP's mind.
Aug
17
comment Why are exception specifications bad?
@supercat: No, I don't know any such languages, sorry. Regarding exception type as criterion for determining whether or not to catch, you can always use a single exception class in your app and use data from its properties to decide.