Author Topic: How to plan/structure interrupt-based code?  (Read 45447 times)

0 Members and 1 Guest are viewing this topic.

Offline NorthGuy

  • Super Contributor
  • ***
  • Posts: 3579
  • Country: ca
Re: How to plan/structure interrupt-based code?
« Reply #125 on: October 13, 2020, 09:45:33 pm »
In computer science, we don't *create* programming languages but *study* them.

The science not only studies things, but also teaches. The students spread around, some of them become engineers, others post on the forums, write blogs, or whatnot. So, the science has a strong influence on our life.
 

Offline Fixpoint

  • Regular Contributor
  • *
  • Posts: 105
  • Country: de
Re: How to plan/structure interrupt-based code?
« Reply #126 on: October 14, 2020, 09:22:36 am »
In computer science, we don't *create* programming languages but *study* them.

The science not only studies things, but also teaches. The students spread around, some of them become engineers, others post on the forums, write blogs, or whatnot. So, the science has a strong influence on our life.

Well ... *people* teach. Not science teaches, but people teach. And those people can do what they want. They have different mindsets, different understandings, etc. So, some will teach good stuff, while others will teach crap.

I observed that people who write blogs or make YouTube videos most often do not rely on academic knowledge but on their own (mis)understandings and will "teach" their audience pretty ridiculous stuff. Actually, it would be nice if those people had deeper knowledge and understanding of things, but ...

Additionally, at universities, there is a very simple yet fundamental problem. Professors (and their assistants) have to teach many subjects that are far removed from their own specialty. For example, a CS professor who has specialized in logic might have to teach an introduction to software engineering at some point. With high probability, the lecture will be a disaster, but that's how it is. So, students might be taught wrong things because of the system. But that has nothing to do with CS itself.

You have the same problem in electrical engineering. When a professor of electrical engineering has to do a course about software engineering, it will likewise be a disaster with high probability. Simply because an EE professor is a specialist for EE, not software. But again, that's the academic system. It always assumes that a professor is some kind of genius who understands everything perfectly and can teach everything perfectly.

During my academic time, I myself was forced to teach a certain course that I was not a specialist in. I did my best, but I think other guys might have done a better job. That's how it is. Unfortunately.
 


Share me

Digg  Facebook  SlashDot  Delicious  Technorati  Twitter  Google  Yahoo
Smf

 

- - -
-->