How much code documentation is a symptom of bad coding (i.e. poor method or variables names, poor class or package structure, missing logging, etc)?
What are the cost vs. benefits of creating interfaces and how should they be balanced? I am only considering cases where interfaces are optional and aren’t needed.
Simplify interaction: Easier to see how to use a List than an ArrayList
Make testing easier because replacement implementations can be used
Can make future changes easier
Harder to understand what the code is doing...
Is it more secure to allow the browser to save a website password or prohibit the browser from saving the password?
Benefits of allow the browser to save the password:
Spoof websites are more easily detected because the username and password don't show up (this may be a mute point if the username is saved but not the password).
Keyloggers won't pick up the password if you don't type it. (Thanks...
What should be in a source control commit message for a single file add?
Reason: The reason for the file should be in a comment in a file so it would be a duplicate to also include in the commit message.
File add: Already part of the commit
Could java.util.concurrent.lock.Lock use a static list of all threads that have locks and ThreadLocal locks lists to know about all in use locks and then check for incorrect order when lock() is called.
Check the ThreadLocal list and if there are no other locks then proceed.
Else if there are other locks then look through other threads to determine if any have any of the same...