For me the key work skill is a willingness to answer "I don't know".
People that can't say that when they don't know the answer are inevitably pompous time-wasters.
People that can't say that when they don't know the answer are inevitably pompous time-wasters.
I think I need help writing specifications for my fellow developers.
I don't know the specifics of what your dealing with but it might be defining a common starting place like an API contract with some architectural/non-functional requirements on the implementation or more recurring things like coding style guides or other documentation.
He was very quick to say "I don't understand" or "could you explain that in simpler terms" - I particularly remember him being utterly delighted by the Unix "fork" system call.