Reputation
Top tag
Next privilege 5,000 Rep.
Approve tag wiki edits
Badges
1 18 34
Newest
 Guru
Impact
~206k people reached

Mar
23
comment How much pair programming is ideal?
@JörgWMittag Sounds like a recipe for a highly stressful work environment for the many introverts doing software development...
Mar
23
comment How much pair programming is ideal?
@JeffO Not necessarily. For introverts, the time spent programming alone is refreshing and pleasing and lets them get in "the zone", and it's also probably why the got in programming in the first place. Doing this mostly with another person watching over your shoulder, constantly talking and discussing things, is highly stressful.
Mar
23
comment Why do so few languages with a variable-type 'operator' exist?
Not sure why people are getting fixated on overloading. The original question isn't about overloading. It looks to me to be about operators as first-class values. In order to write $operator1 = + and then use it an expression you don't need to use operator overloading at all!
Mar
23
comment Why do so few languages with a variable-type 'operator' exist?
Note that metaprogramming, while interesting, isn't necessary in order to support what the OP is asking about. Any language with support for first-class functions is enough.
Mar
18
comment Using a git repository as the base of a new project
If you fork or clone you (normally) keep the history. That may not be what the OP wants if he just wants to use a random project as a start template.
Mar
17
comment Are for loops allowed in the “Clean Code” set of rules?
Keep in mind many programmers don't take anything Uncle Bob says as gospel. I've read enough embarrassing posts by him about functional programming, for example... :/
Mar
17
comment Why should a language prefer indentation over explicit markers for blocks?
@MiguelvandeLaar The language designers can post here (it has happened before), so that's still not a subjective question.
Mar
17
comment How to convince “old” co-workers of the merits of OO for certain applications
Be open to being convinced that maybe OOP isn't the best approach in this case. Maybe if your coworkers were familiar with StackExchange, they'd be asking the question "How to convince this stubborn coworker that OOP shouldn't be used in our project" :P
Mar
16
comment Can a purely declarative language cause runtime exceptions?
To elaborate on @RobertHarvey's comment: a common problem would be non-termination, a program that loops forever. You can hang the computer with Prolog :)
Mar
16
reviewed Reject Can a purely declarative language cause runtime exceptions?
Mar
16
reviewed Approve GPL dictionary usage in commercial application
Mar
15
comment Proper use of break;
"Debug my code" sort of questions are off-topic here. Maybe this is on-topic for StackOverflow. In any case, which do you expect to be the terminating condition in your program? break only exits the inner-most loop.
Mar
15
comment When comparing a string variable to a string literal with .equals(), is there a standard practice for the order of items?
-1 This isn't the reason for the Java convention for equals. Unlike in C, the problem for Java is that the expression x.equals(y) will throw a NPE when x is null. If you have a String literal "something" and you want to consider the case null as "not equals", it makes sense to write "something".equals(y) if you don't know whether y can be null. This will never throw an NPE.
Mar
15
comment When comparing a string variable to a string literal with .equals(), is there a standard practice for the order of items?
-1 "something".equals(str) is considered an acceptable practice in many Java shops.
Mar
14
comment Why didn't == operator string value comparison make it to Java?
@Blrfl It was a rhetorical question; I'm not actually asking about + vs == (I know how they work and why, I'm not a Java novice), but instead pointing out it's false this is about operator overloading. Read the currently accepted answer to understand why.
Mar
14
comment Why didn't == operator string value comparison make it to Java?
@Blrfl Sure. I'm saying the "Java has no operator overloading" part of your answer is a red herring.
Mar
14
comment Why didn't == operator string value comparison make it to Java?
Sure. But Scala is way closer to Java than Visual Basic. I like to think Scala's designers realized that Java's use of == was error prone.
Mar
14
comment Why didn't == operator string value comparison make it to Java?
It wasn't a dig at your answer. It was just a comment. I was just pointing out that a more modern language than Java took the chance to redesign the meaning of ==, just as you mentioned at the end.
Mar
14
comment Why didn't == operator string value comparison make it to Java?
@Blrfl Indeed, that was my point. Since + is a special case, so could have been ==. Having it compare String references instead of comparing Strings has nothing to do with operator overloading.
Mar
14
comment Why didn't == operator string value comparison make it to Java?
Note that other modern languages on the JVM, such as Scala, use == to mean "equal strings".