Tweets of the month

A deadline is a line you cross dead-tired... and missing the people you love the most...
25 Jul

RT @joanappardal "Stressed is just desserts spelled backwards!"
22 Jul

Pente 4
22 Jul


(European) First Aid manual http://www.efam.be/
16 Jul


Graphviz is very nice tool
13 Jul

Kaiten sushi fan
4 Jul

Is there a general way to code to avoid concurrency problems?

(...) Brian Goetz pointed it out to me. (...) The technique is to never write any multi-threading or synchronizing code, except in specialist classes which handle all the issues under the covers.

Ideally, you use what has already been developed by the experts out there: use ConcurrentHashMap rather than HashMap as your default Map; use a BlockingQueue to pass things between threads without having to think about synchronization to share the data; GC is dirt cheap now for short-lived objects so don't think twice about copying out data to a temporary object for manipulation or iterating; and so on.

(...) Inevitably you will have to write some classes yourself that handle concurrency issues. (...) You should isolate that concurrency managing code into separate dedicated classes and, most importantly, spend a lot of time getting those classes right and reusable because concurrency is hard, even for the experts.

--Jack Shirazi

http://www.javaperformancetuning.com

A good paper

A really good paper is one that sparks new ideas in the reader's mind about his own work

Joana Paulo Pardal