addressalign-toparrow-leftarrow-rightbackbellblockcalendarcameraccwcheckchevron-downchevron-leftchevron-rightchevron-small-downchevron-small-leftchevron-small-rightchevron-small-upchevron-upcircle-with-checkcircle-with-crosscircle-with-pluscontroller-playcredit-cardcrossdots-three-verticaleditemptyheartexporteye-with-lineeyefacebookfolderfullheartglobe--smallglobegmailgooglegroupshelp-with-circleimageimagesinstagramFill 1languagelaunch-new-window--smalllight-bulblinklocation-pinlockm-swarmSearchmailmessagesminusmobilemoremuplabelShape 3 + Rectangle 1ShapeoutlookpersonJoin Group on CardStartprice-ribbonprintShapeShapeShapeShapeImported LayersImported LayersImported Layersshieldstartickettrashtriangle-downtriangle-uptwitteruserwarningyahoo

Re: [ljc] Concurrency, multi-threaded programming: under the hood

From: Wesley H.
Sent on: Saturday, March 16, 2013 4:22 PM
Hi Barry, 

Interestingly enough, if I am talking to a company that continually stresses the need for concurrency skills, then it is actually a little bit of a red-light. That depends a bit on the company, because some people are solving problems where concurrency is a fundamental part of the problem, where it is not, a major focus on this as a topic actually screams something like, "We are in a real mess, we have built this system, hadn't considered multi-user testing, now discovered that it doesn't scale, and have decided to try to throw hardware at the problem!". 

That probably isn't all that helpful, so I will try to improve upon that...

In my view, a *good* answer to the, "how well do you know Java concurrency?" question is this...

"I am familiar with the java.util.concurrent classes, and I have read 'Java concurrency in practice', generally though, I find that if you maintain good design fundamentals, lean strongly towards immutability, which is a practice that has other advantages too, and isolate concurrency management in specific areas so that the vast majority of the code-base can be written without reference to concurrency techniques, then concurrency problems becomes far easier to solve. Writing custom concurrency code is a difficult and time-consuming task, and the cost of ownership of concurrency management code is much higher so it is also important to make sure other techniques are considered, with the requirements in mind, of course"

It can also be the case that, when people talk about concurrency they are really referring to problems like transaction isolation and database locking, which is a much more complicated topic in my opinion. They may also have other performance tuning techniques in mind. What might be being said here is, "We have found ourselves in a bit of a mess (which may or may not be self-inflicted), to get out of it, what we really need is a highly experienced and expensive software architect, but getting funding for that would require us to admit our problems, so we are trying to disguise this hire in the form of simply expanding the development team". This problem, I don't really know how to solve.... 

I know that some of that sounds pretty cynical, and I am quite open to be told, "You are wrong! That's not how it works at all!!", but I have this little feeling that some of my developer friends reading this might just be nodding along in silent agreement, and excessive honesty can be a flaw of mine at times ;)

For your purposes, if you have a candidate going for a role that has concurrency as a top level requirement, ask them if they have read, "Java concurrency in practice", and if they have not, advise strongly that they do, since it should give them the tools to answer some of the more tricky questions, and then.... pray for them ;)


On Sat, Mar 16, 2013 at 2:36 PM, Barry Cranford <[address removed]> wrote:
Hi all,

We are often tasked to find Java developers with an understanding of low level core Java. Not necessarily specialist contractors at 5-600 pday, but permanent developers, one may classify as mid-senior level (40-60k). When pushed this is often defined by developers that understand what is going on 'under the hood' e.g. not just how to use popular frameworks but those that understand the concepts and principles beneath them. Whilst some companies will be a little more easy on practical experience, they will push for an understanding. 

Many developers don't make it through interview processes with feedback coming up time and again around a lack of understanding of multi threaded programming and concurrency. I have seen a few conversations recently on the list around these areas so I'm keen to understand the thoughts of the community on this. 

A few things I'm curious about...

- If we could put on some deep dive talks what subjects would you personally most like to have covered?
- Why are some developers drawn to this deeper level and why do some people seem to grasp these concepts so easily against others? 
- If you could offer advice to students starting out in Java development today, how would you suggest learning the fundamentals of these concepts? (reading, self study, projects, talks, oss, something else)?
- Have you been through this learning process in the past and had a eureka moment? What happened for you personally.

If you have any opinions on any of the above please feel free to reply to me personally at [address removed] or through the list. 

Enjoy your weekend!

Kind regards,
Barry | [address removed] | LinkedIn | Skype barrycranford | [masked] |
| Office [masked] |  Fax: [masked]

For all our latest jobs, visit

RecWorks Ltd  |  Registered in England and Wales. Registered No. [masked] 

Email disclaimer: This email contains information which may be confidential. It is for the exclusive use of the intended recipient(s). If you are not the intended recipient(s) do not copy this communication, or disclose it to any other person. If you have received this email in error please notify the sender immediately, delete the message from your computer system and destroy any copies.  Except where this email is sent in the usual course of our business, any views or opinions presented are solely those of the author and do not necessarily represent those of RecWorks Ltd. Although RecWorks Ltd operates anti-virus programs, it does not accept responsibility for any damage whatsoever that is caused by viruses being passed. Replies to this email may be monitored and/or recorded by RecWorks Ltd for operational or business reasons.

Please Note: If you hit "REPLY", your message will be sent to everyone on this mailing list ([address removed])
This message was sent by Barry Cranford ([address removed]) from LJC - London Java Community.
To learn more about Barry Cranford, visit his/her member profile
Set my mailing list to email me As they are sent | In one daily email | Don't send me mailing list messages

Meetup, POB 4668 #37895 NY NY USA 10163 | [address removed]

People in this
Meetup are also in:

Sign up

Meetup members, Log in

By clicking "Sign up" or "Sign up using Facebook", you confirm that you accept our Terms of Service & Privacy Policy