Dylan Cavers created a project to educate others on how to write more robust, bug-free SYCL code, something that is not always obvious how to do when first learning a new API. In this blog, Dylan gives us their motivation behind the project, negative SYCL tests that showcase bad SYCL code, synchronization mistakes, differences in implementation-defined behavior, feature misuse, and implicit behavior not written explicitly but happens as a side-effect.