I have a bone to pick with the developer who decided on the Sametime error messages…

Who decided that the error message shown when trying to connect to a “limited use” Sametime server using the Sametime Connect client should be “Wrong password”? I would really like to meet that developer in a dark alley! We have spent the better part of a day trying to figure out why some clients could connect and some couldn’t. Arrgghhhh… (Of cause it would have helped if the customer had told us which Sametime server was installed but still.)

While we’re rounding up Sametime developers – maybe we should try to find the person who decided that Sametime should use hex error codes you can only find in the API documentation!

Sorry for the rant.

Published by

lekkim

Positive, competent, out-spoken, frank and customer focused architect and developer with a strong foundation in web, cloud and product development. I'm a strong advocate for API first and cloud based solutions and development. I have a knack for being able to communicate and present technically complicated matters in conference, customer and training settings. I've previously acted as team member and leader in a product organisation.