
Thijs Kok is Lead Software Developer at TestMonitor. From the first line of code, he helped shape the product—leading a team that built it from the ground up. With a background in Information Science and 16+ years of experience in software testing, usability, and product design, he blends technical depth with a strong user focus. He believes “good programmers write code for humans first and computers next,” a principle that guides his work. Thijs is passionate about creating software that’s intuitive, effective, and enjoyable to use.
Recent Posts by Thijs Kok:
It may seem like a minor element of software testing, but consistent and clear naming conventions play a key role in organizing complex test elements, easing collaboration, and simplifying traceability …
Read StorySummary: Explore key testing terminology—like test cases, test suites, and traceability concepts—defined and contextualized within TestMonitor to help users understand, organize, and manage their testing processes using a clear, standardized …
Read StoryTestMonitor is designed to simplify the test management process, promote collaboration, and help improve the overall quality of software development. One of the unique ways TestMonitor empowers users is to …
Read StoryNo matter the size or scope of your project, keeping stakeholders informed is crucial for success. This communication ensures that everyone involved is aware of progress, challenges, and resolutions. One …
Read StoryIntegrations can significantly optimize your testing workflows, and TestMonitor offers a variety of options to help streamline processes, enhance collaboration, and increase efficiency. Here's a glimpse into what you can …
Read StoryEfficient test management is crucial to keeping projects on-track, on-budget, and on-scope. During a development effort, you don’t have to be a certified project manager to feel bound to the …
Read StoryWhy are weekly summaries important for software testing and quality assurance? Next to sound processes, effective project management and communication are paramount in quality assurance. One way to elevate all …
Read StoryNo project is immune from risks that, if realized, could impact its schedule, budget, or ability to meet its objectives. However, by proactively identifying risks and then documenting the potential …
Read StoryRequirements are specific, pre-defined descriptions of a feature, capability, or constraint that software must possess to meet the needs of its users. Along with risks, requirements are often the starting …
Read Story