Michael James Bagley

"As mentioned above, you effectively prioritize your bugs and do a great job of collaborating with peers. (Junior Peer) has mentioned to me that you have been a huge help to him as he is stating his career. Look for more opportunities to both mentor and be mentored. You are better at somethings than others and others are better at other things than you are. Let's keep this cycle active."

"I can't think of a major case where you have failed to ask peers and leaders about an implementation and have instead made a bad assumption. Great job."

"Your schedule has been busy for the last 5 months, and you have done and amazing job at juggling all of your responsibilities. You prioritize correctly, and I have no concerns about your judgement here. You've put in the time and effort to make sure this game gets done, and your dedication has not gone unnoticed."

"Mike demonstrated an ability to come onto a challenging project and make a difference. The achievement can be held up against other engineers that did not have similar levels of success when put in a comparable situation. Mike's initial progress was slow, but he continued to gain momentum and became more comfortable with the working environment. He has also carried this momentum into his current project and is making positive contributions within the team."

"Mike was relentless in his efforts to complete the tasks that he was given on the (Named) project. Sometimes the efficiency at carrying these challenging tasks out was not completely meeting expectations. However, he continued to make progress in his areas and see it through to completion."

"... and I have heard more than once how grateful the other engineers are that he has taken the time to not only put so much time into the FSM tool, but to train others how to use it. The saying "teach a man to fish..." is a good way to describe how Michael has helped the team this year."

"Overall, I think Michael is one of the hardest workers in the studio and it is a pleasure to work with him."

"Michael is always willing to jump into trouble shoot and help others. He has a deep and rich background that allows him to think about how new features may impact the system and/or process allowing him to make system recommendations. He is constantly learning new development processes and methodologies on his personal time, which helps guide his thinking and feedback. Michael puts great attention to code conventions, clean and readable code and improvement suggestions for the codebase overall."