After more than 30 years of professional software engineering experience, I have to say that the software model described by this document is applicable and/or useful to only an extremely narrow subset of software in general. I would not recommend taking this advice too seriously.
This is a textbook for the introductory programming course, the first programming experience for many students. Maybe it would be better titled, "How to solve the programming exercises in an introductory course"
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.
If there is any profession that is built on the assumption that its practitioners constantly put aside time to stay up to date it is every profession that is even remotly connected to engineering.
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.
blowski|2 years ago
* https://news.ycombinator.com/item?id=35784167
* https://news.ycombinator.com/item?id=35478871
* https://news.ycombinator.com/item?id=32146245
* https://news.ycombinator.com/item?id=16561815
kiitos|2 years ago
jonjacky|2 years ago
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.
andric|2 years ago
w4lker|2 years ago
cuchoi|2 years ago
pratik_kanthi|2 years ago
atoav|2 years ago
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.
zelphirkalt|2 years ago
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.
layer8|2 years ago
curious16|2 years ago
ofou|2 years ago
samjohnation111|2 years ago
[deleted]