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

Jun
12
comment Is it customary for software companies to forbid code authors from taking credit for their work? do code authors have a say?
It mostly depends on where you are in the world. Law varies from place to place, so where are you to start with?
Sep
10
comment How to Implement Error Handling
@MainMa: Many thanks.
Sep
10
comment How to Implement Error Handling
@MainMa: In relation to exceptions in XML documentation, would you suggest to mention every single exception that can be thrown by any method called by the current method, or only exceptions thrown by the current method itself?
May
15
comment Naming functions that retrieve a value
Yes, I understand that; you made it clear in your answer and your comments. I am just stating my views, which are different, and justifying why. All good.
May
15
comment Naming functions that retrieve a value
See? That's confusing. ;-) If setter is "set", you want getter to be "get" for the sake of consistency.
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
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.
Jan
3
comment What is Developer Anarchy?
What a lovely buzzword!
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. :-)
Oct
26
comment How do we know to favour composition over generalisation is always the right choice?
Ever heard of semantics?
Oct
10
comment how to convince manager to allow stack overflow
Is Dlbert your middle name? ;-)
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.
Aug
14
comment Sporadic unittests or TDD?
@jimmy_keen: Then I must have misunderstood; sorry. In that case, what do you mean by "full testing"? How can you achieve such a thing?
Aug
13
comment Sporadic unittests or TDD?
There is no such a thing as "full testing". Testing can never demonstrate that your code is bug-free.
Aug
2
comment Why do game developers prefer Windows?
@Giorgio: Granted; great development tools and reasonable APIs are important too.
Jul
25
comment Are unit tests really that useful?
"If you practice TDD, your code is created testable—in other words, nice and clean". Ha. Testable and "nice and clean" are very different things. Unit tests interact with the outer interface of your code, which can still be an ugly mess inside. So no, TDD and testable code does not mean "nice and clean".
Jun
1
comment Why do some programmers think there is a contrast between theory and practice?
+1 This answer is good. However, I think it doesn't address the issue of the differences between theory and practice. ;-)
May
28
comment Where could Distributed Version Control Systems currently be in Gartner's hype cycle?
@gnat: I don't deny DVCS' merit in that respect. But the Hype Cycle model assesses maturity plus expectations together; a technology may be quite mature, but if expectations about it are extremely high, it can still be disappointing (hence disillusionment). In my opinion, the expectations about DVCS have been way higher than what it has delivered. In addition, DVCS may have been used in Solaris and Java projects, but that does not mean that its maturity and expectations are balanced. Hence high hype.