To teach in aviation in the US, you need a Chief Flight Instructor (CFI) rating, where you demonstrate to an examiner how to teach the various maneuvers.
IT could learn a lot from regulated industries like aviation.
You can either have a dynamic field or a mandatory curriculum. Once the curriculum is fixed, the field advances at the speed changes can be pushed into the curriculum, which is at best annually.
Not googling how to teach, but skipping the entire "teaching" process altogether.
> It's easier to pick a good teacher than to train one: Familiar and new results on the correlates of teacher effectiveness
> Neither holding a college major in education nor acquiring a master's degree is correlated with elementary and middle school teaching effectiveness, regardless of the university at which the degree was earned. Teachers generally do become more effective with a few years of teaching experience, but we also find evidence that teachers may become less effective with experience, particularly later in their careers. These and other findings with respect to the correlates of teacher effectiveness are obtained from estimations using value-added models that control for student characteristics as well as school and (where appropriate teacher) fixed effects in order to measure teacher effectiveness in reading and math for Florida students in fourth through eighth grades for eight school years, 2001-2002 through 2008-2009.
https://www.researchgate.net/publication/227414368_It's_easi...
http://www.hks.harvard.edu/pepg/MeritPayPapers/Chingos_Peter...
but software engineers? definitely.
The parent comment called it IT, so I called it IT, but if use the more specific term "software engineer" I'm still going to say that most software engineering projects aren't likely to injure people when they fail.
Software engineering just doesn't seem to fall in the category of jobs where you'd want to mandate ongoing training... jobs like pilots or psychologists.
a lot of them even in their free time.
You could spend years at a company working with internal frameworks or internal forks of old open-source projects, and when you change jobs, you realize that everyone's using React and all of your experience is with some half-baked alternative to Rails that someone at your last company cooked up in 2008.
Or you could even be a bona fide OS/360 wizard who hasn't touched anything else for the past thirty years, who suddenly finds themselves looking for a new job--not that there's zero demand for OS/360 experts, but it can be very tough to find positions.