Software Test/Automation
How can I ensure that my code, program, or software is functional and secure?
Testing is the most direct way to ensure quality, but it requires setting ego and pride aside. The goal is to actively prove whether the code behaves exactly as intended, and just as importantly, that it does not do anything unintended. This is why independent testing teams are so valuable. Testing also needs to be treated as a first-class activity: tests should be integrated into CI pipelines so they run automatically as part of every build. If tests fail, they should be investigated and fixed rather than disabled or ignored, ensuring the build remains trustworthy and secure.
How do I interpret user needs and incorporate them into a program?
Understanding user needs can be challenging because users often struggle to clearly articulate what they want. Techniques like the 5 Whys during elicitation can help uncover the underlying needs behind surface-level requests. Another effective method is shoulder surfing, which entails observing users interact with existing software and asking why they perform certain actions or prefer specific features. Creating mock-ups or prototypes is also valuable, as it allows users to provide early feedback and helps prevent major missteps before the software is fully developed.
How do I approach designing software?
I approach software design with a sense of naïve curiosity when engaging with the person presenting the idea. This mindset encourages open discussion and helps them better communicate their vision. Often, clients don’t have every detail defined at the start, and effective elicitation can help them refine and expand their ideas. For this reason, I consider elicitation to be the most critical step in requirements gathering, as it lays the foundation for all design and development decisions that follow.