I was working as a Junior Backend Developer in Electrodomésticos Bombay from October to December 2020. I was working with PHP, MySQL, SQL, MS Access and CSV technologies (and we also tried Node.js and Express.js) in order to automatize orders and providers, with its respective log system etc. The fact is that is was my first job as a Backend Developer, and, at first, It was kind of hard to me to code and to find solutions to the requirements the company wanted for its app. But, little by little, specially reading documentation and asking doubts on Stack Overflow, I could be able to improve a lot my code, my speed of coding etc. So, I am really happy not only because my performance was great, but also because I learnt a lot about the technologies I worked with.
In those cases empathy is really important. I think is crucial to assess which reasons are behind the poor performance of the workmate that are taking you to give difficult feedback. After your individual assessment (and production of hypotheses), it is necessary to assess the performance with the other person, to produce with him other hypotheses about his poor performance (that might be or not the same ones you produced before on your own) and to reach an agreement of behavioral change, in order to improve the performance. That would be assessed periodically till the performance has the right level.
To put my talent on the wrong market, I mean, of course I love Psychology, but after all this time I have realised that (like languages) I need something more stimulant, with more changing demands not to get bored. And that has also to be with the fact that most of the people don't know what a Working and Organizational Psychologist does. So, when I fell in love with web development, I realised it was the right place to be, because I had fun all the time, and it is something really easy to combine with my psychological and linguistic skills.
My change from Psychology to IT was not easy at all. It was hard to accept that I had been 9 years of my life walking in a way that would not fit my desired life style, and that I really loved IT, and the fact that changing to IT meant to start from the beginning in a new field. Will I be able to be a good developer? Am I right? Am I wrong? You never know if the decision you take is good or bad until some time has gone by. And, on the other hand, I was back to study, so that also meant some economic difficulties. How did I deal with it? I had made my mind up, and I was in love (and I feel still the same) with the code so... Like Victor Frankl said, "if you have a 'why' to live, you can bear with almost any 'how'". And that is what I did: I worked giving private lessons of languages during that time. And I studied a lot in order to be able to work as soon as possible. So, it was a hard time, but It was totally worth it: I finished my studies, I am a web developer right now :)
I always handle the mistakes in the same way: understanding of why this is a mistake and learning from it, assessment of any other possible solutions and choice of best option between all the possible solutions. And, obviously, implementation of it.
I assume from the very beginning that is totally impossible to count on any other member of the team so... I would stablish priorities and I would assure to deliver the most prioritary tasks before the end of the day. But, I think the most important thing related to this is that situations like that cannot happen frequently, because they are an indicator of lack of organization. So, I would work with my team on the underlying factors that have provoked this emergency delivery in order to this situation not to be repeated again.
I will tell you not just one, but two ones: