This week I read a blog post from TestLodge talking about the characteristics that make up a good software tester. The post found at https://blog.testlodge.com/characteristics-good-software-tester/ helps identify some of the attributes that a tester should have in order to be proficient in their testing as well as excel in their career. I chose this post because it provided a different perspective than most. As a student initially learning these skills I often get too focused on how to do different testing procedures and sometimes forget to look at why I’m doing them and what purpose do they have. Articles and posts like this help me to take a timeout and look beyond the skill set that I’m trying to acquire to help put me in the right state of mind. The post breaks it down into 13 different characteristics. Characteristics like testers have to be a strong communicator and be a team player. This is good to remember, especially early on in our careers, so that we don’t ignore failed tests or improperly communicate what failed in the software to the rest of the development team and let an inferior product be released simply because we were to scared of upsetting someone by telling them part of the code is wrong. Other characteristics like thinking creatively and paying attention to details. These attributes will help us examine closer what the goal of the test that we need to write is and think outside the box in order to write the most effective test. We need to be able to realize that just because we did a test a certain way in class for a project one time, that may not be the best way to write the test every time. A good tester should also be organized and should meet deadlines. Time management is crucial in the software development process. Staying organized with all your tools, notes, and team communications will allow you to complete more tests. It will also help you keep track of your deadlines and prioritize your tests so that way you are not delivering a product late of missing important tests and creating too many tests for less important features. I felt like this post is good to revisit from time to time so that I don’t get too focused on just trying to write a perfect test and develop a broader skill set that allows me to recognize the right approach to each situation and to stay organized without rushing into a project and failing from the start.