Testers frequently face problems associated with excessive emphasis on formal, procedurally scripted testing. Politics, bureaucracy, and paperwork combine with fixation on test cases. Project managers and internal auditors mandate test cases structured and written in a certain form “because FDA”. When someone tells you this, it’s a pretty good indication that they haven’t read the FDA’s guidance documentation.

Here’s an update on how things are going with version 8.0, and our plans for releasing and finalizing Ivy.

My career has meandered its way not into the biological or physical sciences, but into something we’re currently calling site reliability engineering – a strange amalgam of systems administration, performance management, software development, quality control, and the crafting of antifragility, a practice I don’t really know what to call other than “applied statistics”. In the narrowest view, SRE can be limited to a fancier name for release management, but in most organizations there is runway to make it much more.

We’re led to believe that we’re able to do a lot with the structured async/await API layer. Some tutorials, while great for the developer getting their toes wet, try to illustrate real world examples, but are actually just beefed-up “hello, world"s. Some even misuse parts of asyncio’s interface, allowing one to easily fall into the depths of callback hell. Some get you easily up and running with asyncio, but then you may not realize it’s not correct or exactly what you want, or only gets you part of the way there. While there are tutorials that do to improve upon the basic Hello, World “use” case, often times, it doesn’t go far enough. It’s often still just a web crawler. I’m not sure about others, but I’m not building web crawlers at Spotify.

Yes, Python is known for being "slow" in some cases and the good news is that this doesn't really matter depending on your project goals and priorities. For most projects this detail will not be very important.

However, you may face the rare case where a single function or module is taking too much time and is detected as the bottleneck of your project performance, often happens with string parsing and image processing.