3 ms·
I think many of us learned the other way 'round. (1) Start off by making changes to a program that someone/some book gave us as a basis and blindly stumble thr
by wyldfire 11y ago
I think many of us learned the other way 'round.
(1) Start off by making changes to a program that someone/some book gave us as a basis and blindly stumble through some changes and compiler/interpreter/runtime errors.
(2) Take a step back, absorb what we've learned from the errors.
(3) Read more about the principles of the programming language/OS/API/operating environment.
(4) Internalize concepts behind the language/OS/API/operating environment.
(5) Goto (1).
It's only after many iterations through this process that I can now see similarities among different processors (CPU/DSP/GPU/etc), operating systems, APIs, programming languages. So many classes of problems can be solved effectively without ever understanding these details, so it makes sense for those new programmers not to learn the details at first. IMO, this is at least an intermediate-level text.