Okay, so explaining the solutions to a different non-technical stakeholder. I have done this many times in my previous and current experience as well. So, basically the managers are the product, they are product owners, they are mostly non-technical guys and how do we ensure that they understood the problem statement that we are facing is by drawing the things. Basically, we draw the charts, graphs, we take help of a draw.ipo or you can, there are multiple Lucid flows, we can use Lucid and the draw.ipo, all those things we can use for sure. And I am used to explain what kind of a technical challenge in a meeting to them. Once I draw the flow diagram, I used to set up a presentation with them for this kind of a solution. This is what problem statement is and this is what solution is. And based on the cross questioning they have with me, I used to understand that yes, these people have understood those problem statement and we need this kind of a time and we need to implement this kind of a solution, proposed solution. So, based on their confirmation, we get to understand and there are certain examples, solutions that we provide to them. Based on that, they will get to know what we are thinking or what technical team is thinking of. So, let me give you an example where I have done this. Basically, when implementing the consumption logs from Lambda to Kafka, previously we have decided to use telemetry. Coming to the telemetry, it is open telemetry. Coming to the open telemetry, first they have given me to use the open telemetry for our logging system. Whenever we trigger a Lambda, whenever we start transforming an article, we have to send the logs via open telemetry for our dashboard analysis purpose and that needs to be saved at S3. So, I did some of the POC on that, but the thing was like open telemetry was not suitable for our reach, for our goal. So, I have created a diagram, what is the limitations of open telemetry, what costing it will require, we have to know and what could, if we have to use open telemetry, what changes we might need to do and how much time it will require. Apart from that, I have given a different solution to them that let us use Kafka for that. So, for the Kafka, whatever we need, we have to create a producer of the Kafka in each Lambda that will consume, the data will be created itself in the Lambda and pushed to the Kafka. So, I have created two diagrams, one for the positive case and one for the negative where I was in the opposite of using open telemetry. I have even created a diagram and in the terms of positive way using the Kafka, I have created that diagram flow as well. I have explained them in the flow chart, they agreed to it because they understood what are the challenges with the open telemetry and what are the positive side of using Kafka. The speed of development, the speed of performance and all those things will be much useful to them and they easily agreed upon what I have proposed, what solution I have proposed and that is how it has worked. So, there are a lot many projects where I have proposed a different kind of a technical solutions to a different kind of non-technical guy. So, but this is one of the examples.
