Reputation
2,963
Top tag
Next privilege 3,000 Rep.
Cast close & reopen votes
Badges
15 30
Newest
 Good Answer
Impact
~149k people reached

Jul
23
comment What is the point of having every service class have an interface?
@wrschneider I disagree. Interfaces are less cluttered, since they only expose methods of the contract. There are no implementation details, no private or protected or (accidentally) public methods. An interface simply defines a cleaner contract.
Jul
23
comment What is the point of having every service class have an interface?
@wrschneider Unfortunately Java classes are pretty bad (as in "unclear" and "cluttered") at defining public contracts, which is why interfaces are preferred.
Jul
23
comment Why is modularity a good idea?
But why is a God Object a bad idea? Simply giving it an anti-pattern name won't convince anyone :)
Jul
22
comment Who should write Unit Tests?
@KonradMorawski "she" is a generic placeholder, it doesn't imply the programmer is actually female. I've seen it used in many programming books as a way to balance the use of the generic "he" (which also doesn't mean the programmer is actually male).
Jul
19
awarded  Good Answer
Jul
17
comment What is the meaning of “doesn't compose”?
It's closer in meaning to function composition than to object aggregation.
Jul
16
comment Isn't there a substantial problem with SVN tags?
You can clone a single branch with git. Other than that, I agree with your answer.
Jul
16
comment Is the function using python list comprehension, stateless?
Where do you think you see state?
Jul
13
reviewed Approve Is the question “What is the using statement” a bad question to ask an interviewee?
Jul
13
reviewed Reject How to write a very basic compiler
Jul
6
comment Advantages of these recommendations in ooprogramming using Java
@overexchange Any book on OO design and programming will probably do.
Jul
6
comment Advantages of these recommendations in ooprogramming using Java
This should be closed because it's too broad. If the answer to this question can be a book's chapter about OOP design practices, then it's probably not for this site. This question will either invite subjective opinion, or will result in long-winded answers where you will be inclined to debate with the author.
Jul
1
comment What's the difference between simulation and emulation
I'd say you got the two concepts mixed up. It's simulation that doesn't care about the exact implementation; emulation cares very much about the internals. See: M.A.M.E.
Jun
23
reviewed Approve Is REST only limited to optimistic concurrency control?
Jun
17
comment Why would a program use a closure?
@supercat I'm probably missing something, but it seems pretty inconvenient and fragile to design shareable objects that way. I'd say it's about as inconvenient as designing shareable closures.
Jun
16
comment Why would a program use a closure?
@supercat Wouldn't the same disadvantage exist with stateful objects?
Jun
12
comment Why pointer symbol and multiplication sign are same in C/C++?
@iammilind A possible compromise would be to close the other question but copy the answer quoting Ken Thompson here (you could post it yourself and accept it)
Jun
12
comment Why pointer symbol and multiplication sign are same in C/C++?
@iammilind Don't take it the wrong way! This isn't something negative about your question. Also, relative age of both questions isn't relevant. I think the accepted answer here is less accurate than one of the answers in the other question (which comes "straight from the horse's mouth").
Jun
10
comment Why would we need to rollback twice before closing in a finally block?
@RobertHarvey I think the OP is asking about the two consecutive rollbacks in the finally block. They seem like a cut-and-pase mistake to me...
Jun
8
comment Why isn't lazy evaluation used everywhere?
Such as? There are reports of significant performance costs when using eager evaluation as well (costs in the form of either unneeded evaluation, as well as program non-termination). There are costs to almost any other (mis)used feature, come to think of it. Modularity itself may come at a cost; the issue is whether it's worth it.