-Lightweight -Durable -Reasonable price
In reality, you can only choose two of these.
16 karma · joined November 6, 2014
-Lightweight -Durable -Reasonable price
In reality, you can only choose two of these.
Suppose an AI assistant is heavily trained on a popular technology stack, such as React. Developers naturally rely on AI for quick solutions, best practices, and problem solving. While this certainly increases productivity, doesn't it implicitly discourage exploration of potentially superior alternative technologies?
My concern is that a heavy reliance on AI could reinforce existing standards and discourage developers from experimenting or inventing radically new approaches. If everyone is using AI-based solutions built on dominant frameworks, where does the motivation to explore novel platforms or languages come from?
I think that with a standard Ablenton project, for example, with several VSTs (this sounds like a Kontakt library) and replacing the midi clips by the Magenta's MusicVAE output for example, you could make infinite variations.
As after all the sound quality doesn't interest me too much to do this, I usually use iZotope RX, but I will try this tool.
Suppose you have to test the irrigation system of a tree in your garden, you want to test how many times and how much water is used, you have two ways to do it:
1) State-based: run the system for a few hours, during which it should water the tree several times. At the end of that time, you check the state of the watered tree: Is the soil moist enough, is the tree well, are the leaves green, etc. (Obviously this is just an example as this test would be complex in real life, but it is to get the idea across).
2) Interaction: We place a flow meter, a device that registers how much water is flowing through the device and at what times. At the end of the day, check that the device has been called the correct number of times, with the correct amount of water each time, and we don't worry about checking the status of the tree.