In the world of software development, there's an ideal realm of best practices and a pragmatic one driven by project needs. The decision to write tests depends on factors like project lifespan and relevance, as insisting on unnecessary tests can delay delivery and harm a developer's credibility. While individual test-writing enhances personal work, enforcing it across a project may not significantly boost overall quality. A skilled developer strikes a balance between business needs and technical excellence, understanding that rigid adherence to top standards isn't always necessary.