1,145 karma · joined January 22, 2019
Let's be real here, there's no way to truly learn music theory without practicing. It's like math, algorithms, you don't have to learn it to compose (if you are talented you can easily cruise on raw talent) but you have to practice with pen and paper (or computer or instrument) to actually learn it. Many replies here focus on the mathematical patterns and relations, they are useful observations but ultimately has little bearing on the actual usage of theory.
They are a group of volunteers who verify and counter advanced fee fraud by wasting their time and increasing opportunity cost.
https://forum.419eater.com/forum/viewforum.php?f=66
They also use the infamous Lenny natural language bot among other methods of automation.
https://gss.github.io/guides/ccss
Do you plan to add a GUI editor too? What do you think of Xcode/Figma's constraint system?
You can use something like https://diez.org/ to provide easy cross platform support. (Note it's only partially open source)
The browser and most "responsive UI" platforms like Flutter have a built-in constraint solver to process layouts. However often the language does not provide sufficiently powerful systems to express constraints in relation to each other, so for the backend you can probably take advantage of existing code when Z3 is too heavy a dependency. (I am not sure if this is possible for all layout solvers, you will probably have to prove it mathematically that the CSS (or whichever platform you are targeting) solver is equivalent or of higher abstraction level in relation to your design language so it can generate the appropriate code. Otherwise the purely declarative approach might not work and you will need JS/Dart/the native scripting language.)
AFAIK only TypeORM and really pricey enterprise database software comes with change management systems like this. Even Rails do not have such conveniences.