For the certification program at Redis University (https://university.redis.com/), we previously used ProctorU because that's what other folks were doing -- proctored exams for certification.
Buuut, after a while, we were like, why subject people to this? This is crazy. And why even charge for certs anyway? I'm happy we're done with proctoring!
Async Python has proven faster in my uses for IO and non-CPU-related stuff. But I think Python, either as a community or within the language, needs to solve the anti-pattern of maintaining separate sync and async versions of a library. I'm thinking specifically of aioredis and redis-py, both of which I've worked on.
Some people are looking at ways to solve this. I know urllib3, elasticsearch-py, and a few others use unasync (https://github.com/python-trio/unasync) to transform async code into sync code, leaving one codebase supporting both uses in different namespaces. This leaves you with some conditional logic (is_async_mode() -- https://github.com/python-trio/hip/blob/master/src/ahip/util...). I'm seriously considering this approach.
Super sad. I interviewed at Samasource early in my career. They had a cool mission, and Ms. Janah seemed really inspiring. Glad she got to do so much with the time she had.
Buuut, after a while, we were like, why subject people to this? This is crazy. And why even charge for certs anyway? I'm happy we're done with proctoring!