>>106966830
old job was advanced process control. go to refinery or chem plants, tune up the loops, make a bunch of test moves on everything in a subunit, model the process, make sure there aren't any numerical oddities, and then place the optimizer ontop of the subunit that controls it and pushes it towards an optimum every minute.
most people in these roles at a site are dogshit at it since they've never built one from scratch and just barely maintain what they have setup. I probably deployed 40 or 50 of them...I don't think it would be terribly difficult to find a job doing it again I would just need to move, which I really don't want to do. Site money is less (~$140-$170k?) but it would be zero stress since I know what I'm doing and it's more or less a blackbox to people.

>his language doesn't have a word for 1.5
languagelets

Should I minify css then purge unused css in the minifed result, or purge unused css then minify the purged result?

Asking cause I am thinking of forking a project which deals in minification to add purging ability, but wondering which should come first in workflow. Aiming to optimize for size of the css and the speed at which it minifies/purges.

In the end the workflow would be either:
Minify --> Purge Unused --> Compress (GZIP or Brotli)
OR
Purge Unused --> Minify --> Compress (GZIP or Brotli)

Thoughts?