I believe this problem is analogous to the door handle that requires a Pull sign.

For example, much of the 'Swing is slow' reputation comes from applications that execute long-running methods on the GUI thread (such as querying the database over the network in the middle of your mouse clicked method). This is obviously a Bad Idea, and it's one that we preach against with regularity in articles and JavaOne talks.

If you have to regularly remind coders, well, you've got something that needs fixing. Threads in Swing are done right in theory but not in praxis, and its the latter the theory needs to worry about (yes yes, about which the latter should be concerned. Thanks, English majors).