Quote:
Originally Posted by Greg McKaskle
Both POV's are very useful. The simple model view lets you efficiently use the tool to write lots of good code quickly. The underlying knowledge of the RTOS and architectures is useful if you work on the LV team or if you are trying to coax the most from it. Focus too much on the details, and you lose sight of the model.
|
It may not seem like it from my posts, but our programmers are spending about 99% focusing on the "model" and about 1% learning about the "implementation". My emphasis on "implementation" (in my posts) is because I want to "vet" in this forum what I tell the students.
The benefit of an underlying knowledge of what is actually happening "under the hood" goes beyond working on the LV team or coaxing the last ounce of performance. It is also useful in understanding the limitations of the model, for example under what conditions will a 5ms task and a 50ms task "play nice". I want the students to come away from this with at least a hint of understanding of how a single computer can (seemingly) be doing two (or more) things at once.
~