Up next chefs will be food engineers, tailors will be clothing engineers, and because I changed the oil in my Toyota once, I’m now a Toyota engineer; specializing in fluids.
Words mean literally nothing anymore (ha). Titles in tech are hilarious at almost every level, especially from the outside looking in.
“DevOps” is at least ill-defined from the very start, so if we have arguments about what “DevOps” means, at least I can learn something.
1. understanding important engineering principals like queuing theory
2. understanding the system in question well enough to modify it to emit relevant metrics for applying stuff like queuing theory
3. collecting this data into timeseries form
4. applying statistical tests to them, e.g. for normality.
5. deciding between a variety of possible anomaly detection algorithms
Another portion involves capacity planning and datacenter design, which requires a certain amount of electrical engineering knowledge, as well as forecasting. A different part of my job simply involves writing software, testing it, and signing off on changes.
Overall it sounds fairly engineery, even if the powers that be would rather prefer it if the term be reserved those who pass an internship and test (but then refuse to expand said test to include new domains).
Probably going to be ridiculed for this, but "clothing engineer" actually sounds "cool" in a very mature market, in my eyes.