I see a lot of value in this. It gives a step-by-step method that students can follow, which often works. The prevailing alternative seems to be, "Look at a lot of examples, pick one that looks similar to the exercise, and change it around by trial and error until it kind of works." This does not generalize to professional level programming either.

At this initial stage, the goal is to build the students' confidence that if they work systematically, they can solve problems. As their education and experience continue, they can take on more realistic problems and methods.

Maybe many software devs don't view themselves as engineers, but engineers can be held liable if their work doesn't live up to the current technological standards.

I would say, regardless of what you do, sometimes you have to take some time for introspection, unless you plan to live with the consequences of not doing it. And reading books is part of that.

If your employer is smart they consider that. If you are smart you also consider that.

Option 2: In lack of option 1, I am afraid one will have to spend ones free time on it.

Option 3: Take a "sabattical" or whatever it is called.

Option 4: Quit job and find an option 1 employer.