June 30, 2009 at 7:24 Higher technical education
After reading this topic , I first commented and then went wild ... no, at first I did go wild, and only then - commented on it, but after that I decided that I wanted to write about it. Therefore, I will give my comment here almost without cuts and edits. (for reference - in the original topic, the author with many errors, both spelling and factual, writes about the optional education in general and technical education - in particular).
Firstly, I immediately mean my ability to talk about the topic raised by the author - I’m 26 years old, I graduated from the university in 2006, and now I work in a large well-known IT company. Who cares - there are details in the profile, but anyway - I understand a little about the topic. I graduated from the 6th faculty of the Samara State Aerospace University, probably not the best in the country, but definitely the best in Samara, and probably in the entire Volga region of a technical educational institution.
What do you think you are taught at the university? No, if you went to some economic or legal one with the goal of killing eight and a half birds with one stone - I can not vouch for the fact that they will teach you something at all, but what do they teach at IT departments?
1. Mathematics. The mother of all sciences, without the knowledge of mathematics, the concept of an engineer is unthinkable, it is the basis for almost everything that you can think of, applicable to computer science.
2. Probability theory, statistics, analysis of random processes. In general, I do not see the need to explain why this is necessary.
3. Physics. I will not talk about the importance of physics as such, but in my opinion, in addition to its own knowledge, it gives the student the first example of how the mathematical apparatus can be applied to solving real-world problems. The probability that physics will be useful to a future engineer is very high, I would rate it at 15-20%
4. A group of "low-level" subjects - electrical engineering, circuitry, interfaces, and the climax - the course "Microprocessors". Sorry, but a software engineer must understand how it all works - and it’s better to understand how it works that he uses at the moment and a couple of alternatives. If you are connected with iron - this is your daily bread, otherwise - there will definitely be no harm from this knowledge (I have come in handy repeatedly).
5. Databases. No comment - you need to know this, even if you don’t work with them. And you need to know not SQL and not “access”, as the author eloquently put it, but understanding how it all works, how it works at the lower level, what is an index, why is it needed, what does it happen, what is a transaction, what is integrity - etc. Without an understanding of these concepts, it seems extremely doubtful to me that the future programmer will be able to use them correctly.
6. A group of "high-level" subjects. The list may vary, but as a rule, this is the theory of formal grammars, logic, functional and declarative programming languages. Incredibly expanding consciousness, and it is very possible that it will be useful in the future.
All this prepares the student for ...
No, not to the diploma. To real life. In life, an engineer will almost certainly have to deal with tasks that have to be solved in a super-tight time frame, under the most severe pressure and the most severe lack of information - study allows him to go through all these circles of hell, gain this experience, and if he also worked during studies, then he will learn to do the hell of a lot of things at the same time, to prioritize, to choose, in the end, the “victim” - something that can be neglected in the circumstances. It is this ability to quickly learn, “digest” wild volumes of information in extremely short time, to draw conclusions in the face of insufficient data (I heard something about it somewhere, but I don’t remember that, but the exam is already underway - to hell with it, logically, it should work like this: ...) - it all makes a universal engineer, a person,
That is why Higher Technical Education is needed - it is it that makes an engineering student out of a student. There are self-taught, I do not argue - but they really will break through themselves, but for us, mere mortals, this will greatly help (helped, and will help) solve our real problems.
PS transferred to the blog the original topic. I understand that I did not list all the disciplines that are vital for the engineer - therefore, add in the comments.
Firstly, I immediately mean my ability to talk about the topic raised by the author - I’m 26 years old, I graduated from the university in 2006, and now I work in a large well-known IT company. Who cares - there are details in the profile, but anyway - I understand a little about the topic. I graduated from the 6th faculty of the Samara State Aerospace University, probably not the best in the country, but definitely the best in Samara, and probably in the entire Volga region of a technical educational institution.
What do you think you are taught at the university? No, if you went to some economic or legal one with the goal of killing eight and a half birds with one stone - I can not vouch for the fact that they will teach you something at all, but what do they teach at IT departments?
1. Mathematics. The mother of all sciences, without the knowledge of mathematics, the concept of an engineer is unthinkable, it is the basis for almost everything that you can think of, applicable to computer science.
2. Probability theory, statistics, analysis of random processes. In general, I do not see the need to explain why this is necessary.
3. Physics. I will not talk about the importance of physics as such, but in my opinion, in addition to its own knowledge, it gives the student the first example of how the mathematical apparatus can be applied to solving real-world problems. The probability that physics will be useful to a future engineer is very high, I would rate it at 15-20%
4. A group of "low-level" subjects - electrical engineering, circuitry, interfaces, and the climax - the course "Microprocessors". Sorry, but a software engineer must understand how it all works - and it’s better to understand how it works that he uses at the moment and a couple of alternatives. If you are connected with iron - this is your daily bread, otherwise - there will definitely be no harm from this knowledge (I have come in handy repeatedly).
5. Databases. No comment - you need to know this, even if you don’t work with them. And you need to know not SQL and not “access”, as the author eloquently put it, but understanding how it all works, how it works at the lower level, what is an index, why is it needed, what does it happen, what is a transaction, what is integrity - etc. Without an understanding of these concepts, it seems extremely doubtful to me that the future programmer will be able to use them correctly.
6. A group of "high-level" subjects. The list may vary, but as a rule, this is the theory of formal grammars, logic, functional and declarative programming languages. Incredibly expanding consciousness, and it is very possible that it will be useful in the future.
All this prepares the student for ...
No, not to the diploma. To real life. In life, an engineer will almost certainly have to deal with tasks that have to be solved in a super-tight time frame, under the most severe pressure and the most severe lack of information - study allows him to go through all these circles of hell, gain this experience, and if he also worked during studies, then he will learn to do the hell of a lot of things at the same time, to prioritize, to choose, in the end, the “victim” - something that can be neglected in the circumstances. It is this ability to quickly learn, “digest” wild volumes of information in extremely short time, to draw conclusions in the face of insufficient data (I heard something about it somewhere, but I don’t remember that, but the exam is already underway - to hell with it, logically, it should work like this: ...) - it all makes a universal engineer, a person,
That is why Higher Technical Education is needed - it is it that makes an engineering student out of a student. There are self-taught, I do not argue - but they really will break through themselves, but for us, mere mortals, this will greatly help (helped, and will help) solve our real problems.
PS transferred to the blog the original topic. I understand that I did not list all the disciplines that are vital for the engineer - therefore, add in the comments.