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 should be in a source control commit message for a single file add?
What are the cost vs. benefits of creating interfaces and how should they be balanced?
Is it more secure to allow the browser to save a website password or prohibit the browser from saving the password?
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.
Do a "requirements document" and "design document" use an outdated format? Is one monolithic document the right way to handle that information? Are there better ways to handle that information?
Consider this idea:
Keep requirements/design info in a tree structure.
Support viewing the whole tree to a specific depth so that people can ignore undesired detail.