To Develop, Or Not Develop`: A Tester's Perspective As a tester who doesn't consider themselves a developer, I have a different approach to problem-solving and testing. I find the unexpected results from combining code and systems fascinating, and I enjoy exploring the interactions between various components of an application. While I can write basic code and understand database concepts, I don't find writing extensive code or solving complex problems in coding as interesting as understanding how things work together and identifying potential issues. I believe testing is a multi-directional talent that involves experimentation, observation, planning, communication, and social engineering to address ecosystem-level problems. Automated testing is an essential tool for me, but I prioritize learning the basics of programming languages and methodologies over becoming an expert in a specific language. My goal is to understand what pieces of the application are doing and how they work from top to bottom, rather than getting bogged down in repetitive coding tasks. I find the process of testing and problem-solving more engaging than writing code, as it allows me to figure out amazing things and learn from those issues.