Re:Saying Sorry When Things Go Wrong [pdf]
by tkahnoski on Tuesday July 11, 2017 @06:23PM
(#14748605)
Similarly "I need help" and "How can I help?" are powerful things.
Re:Saying Sorry When Things Go Wrong [pdf]
by beobab on Wednesday July 12, 2017 @05:40AM
(#14751223)
I still have trouble with "I need help". I can work out what I need to do, but I have trouble doling out work in a way which means that it gets done to the specification I have got in my head, so I am not sure how to accept the offers of help.
I think I need help writing specifications for my fellow developers.
Re:Saying Sorry When Things Go Wrong [pdf]
by tkahnoski on Tuesday July 18, 2017 @03:31PM
(#14799358)
That would be the trick in delegation. Giving others the authority to get things done.
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.
Re:Saying Sorry When Things Go Wrong [pdf]
by arethuza on Wednesday July 12, 2017 @06:43AM
(#14751444)
I learned that habit from the Professor (UK style) I used to work for whose speciality was non-linear control systems and was clearly rather bright.
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.
People that can't say that when they don't know the answer are inevitably pompous time-wasters.