custom.css and quick.css

the quick.css is ideal for fast changings to look whether things work or not.
another css option is given via dashboard – appearance – editior (child-theme css) but i suppose after this

/*
* PLEASE DO NOT EDIT THIS FILE!
* This file is only in your themefolder for WordPress to recognize basic theme data like name and version
* CSS Rules in this file will not be used by the theme.
* Instead use the custom.css file that is located in your themes /css/ folder to add your styles.
* You can copy a style rule from any of your css files and paste it in custom.css and
* it will override the original style. If you just want to add small css snippets you might also
* want to consider to add it to the designated CSS option field in your themes backend at: Theme Options->Styling
*/

this is aswell not the way – but there is anonther file in enfold folder/css/ custom.css

so here is the question: is it advisable to put a minified version of the quick.css into custom.css and upload it – and than delete all the stuff in quick.css after every design and functional work on the website is done.

That means using quick.css only as a temporarily option.

or in other word why the hell is there a custom.css which is definitly not so easy to handle ( download – change something – upload – controlling etc pp) – what are the advantages of a custom.css ?

BTW: Yes there is another great opportunity for custom.css on multilingual Sites ( changings in custom.css work for all languages) – in quick.css it is language specific.