Yes, I get it, it is complicated... but it's not a dark art. Why do you think there are certifications in cloud engineering? They're not a liberal arts degree.
I see them all the time. First of all any certification for :"cloud engineering" generically is worthless. Second, anyone trying to get hired on the basis of one is similarly worthless (although possibly trainable). And third, a competent cloud engineer is probably going to be looking in the wrong place for these issues.
Yes, I get it, it is complicated... but it's not a dark art. Why do you think there are certifications in cloud engineering? They're not a liberal arts degree.
I see them all the time. First of all any certification for :"cloud engineering" generically is worthless. Second, anyone trying to get hired on the basis of one is similarly worthless (although possibly trainable). And third, a competent cloud engineer is probably going to be looking in the wrong place for these issues.
I wrote "certifications" and wrote nothing about them being generic. I didn't say anyone with "Cloud Engineering 101" could solve their problems. Stop putting words into my mouth.
I agree that IT paper qualifications are overblown i.e. companies wanting candidates with PhDs, but little to no practical experience.
Industry certifications (Google, AWS, Microsoft Azure) give you product knowledge, they're significantly more about knowing product offerings and how they work together. Practical knowledge you gain from experience, but understanding what products are at your disposal is half the solution. Understanding how pieces fit together and just as significantly how much they will cost, some services accrue cost based on size, others on traffic, execution time, number of requests or configuration. Managed versus unmanaged. You can set up managed services easily with mouse clicks, but you pay for that ease. In many cases, you're going to need to run comparative tests, but it's not a mystical artform.
And your last point makes no sense. A competent cloud engineer is probably going to be looking in the wrong place?! So an incompetent one will look in the right place? Or you're saying that this problem is unsolvable as both competent and incompetent cloud engineers will be looking in the wrong place?
Comments
I agree that IT paper qualifications are overblown i.e. companies wanting candidates with PhDs, but little to no practical experience.
Industry certifications (Google, AWS, Microsoft Azure) give you product knowledge, they're significantly more about knowing product offerings and how they work together. Practical knowledge you gain from experience, but understanding what products are at your disposal is half the solution. Understanding how pieces fit together and just as significantly how much they will cost, some services accrue cost based on size, others on traffic, execution time, number of requests or configuration. Managed versus unmanaged. You can set up managed services easily with mouse clicks, but you pay for that ease. In many cases, you're going to need to run comparative tests, but it's not a mystical artform.
And your last point makes no sense. A competent cloud engineer is probably going to be looking in the wrong place?!
So an incompetent one will look in the right place? Or you're saying that this problem is unsolvable as both competent and incompetent cloud engineers will be looking in the wrong place?