[klodolph]

"Definitely" what?

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.

[tester34]

Definitely SE is kind of job where people are constantly learning

a lot of them even in their free time.

[klodolph]

Some definitely don't. It's easy to end up with no experience with modern tech stacks after leaving a position. Some environments ossified years or decades ago and make it easy to bury your head in the sand once you're there.

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.