Accept what we know and don’t know…Part 2!

Following on from Monday’s post Accept what we know and don’t know, I found myself getting further frustrated by the insistence of the individual that the solution they wanted to use did not present any issues as this was the solution used by someone else!

I tried to point out that just because someone else used that solution, did not make it the right solution, nor did it make it the wrong solution! However, for me there were security risks with what was being proposed, and while that risk may be acceptable to the other people, I felt it was unacceptable for our solution.

Unfortunately, the person did not accept my feedback despite me highlighting my knowledge/experience in this area, and the damage that may be caused to our reputation.

In a further development, I did some investigation into the solution that the person wanted to use, and found that it should be possible to embed what they wanted to use, in a HTML widget on a webpage, and while that isn’t my preferred solution, it would be an acceptable one. I then did a proof of concept of this potential solution, and found it was possible – result! I sent a screenshot of the example I had written and asked for feedback as I believed this would be an acceptable solution – At time of writing this post, that was more than a day ago…I still await a response!

I must be honest and say, I did not sleep well that night, as I had come to realise that it seemed the person had already decided how they would do the solution because someone else had told them this was the way to go. But what really got me was why they didn’t speak to me in the first place about what they wanted to do, as I would have been able to give them options that would be acceptable in our solution…but for whatever reason they went to someone else first – Someone who knows nothing about our solution, it’s architecture or software, so how on earth were they the ones to advise on a solution for us?!

I now feel that if the person dismisses the option I have suggested, I will need to seriously consider my position/responsibility for our solution, as I do not want to be associated with something that I feel may be a risk. I really do wonder why my thoughts/opinion were not sought when the requirement was first identified. I am very frustrated and a bit annoyed that my professional experience in this area has been completely ignored.

I therefore await response to my proposal, and depending on what that response it, it may mean I need to consider whether I continue to mange this solution, as after all it is something I do for nothing, in my ow time.