Everything is often used interchangeably in a certain context.
A programmer is probably the most concrete: someone who is programmed, that is, sitting at the computer and teaching him something.No statement is made as to whether or not he developed the project. He translates a thought into a programming language.
A developer, on the other hand, probably programmed.But he may also have developed the idea that a programmer then translates. However, ‘developer’ is usually used synonymously with programmers.
The computer scientist differs in principle in IT specialists, FH or university computer scientists.This all merges into one another, but the IT specialist has an education that is usually intended to enable him to programmers. An IT specialist should be able to understand the thoughts of a computer scientist and help him to implement this software architecture as a program. This does not mean that an IT specialist would not be able to build his or her own architecture. That is just not the aim of training. The IT specialist also likes to divide himself as an IT specialist for application development or system integration. With a FISI, I’ve been thrown up in the development of the applications for the first time. Conversely, the same. In system programming, most FIAE are also overwhelmed. But that is also explicitly not the aim of training. Nevertheless, many FIAE are capable of more than the training suggests – out of personal interest.
A software engineer should be able to program to understand the process chain.However, he is primarily responsible for process management in software development. How is source code distributed and exchanged among the different developers, which compilers translate, how is the product built, how do the tests run, how is the quality secured? So it’s not primarily about writing software, it’s about the process of converting the source code written by other sources into a product.
I myself studied “Practical Computer Science” at the FH, which I would translate as “You throw into the cold water”.We had theoretical computer science, we had project management and there was the task, for example, to develop a driver for a PCI card under Linux. Problem with this: Most of them had no contact to Linux or to driver programming at the time and the learned programming language Delphi (or java) was not helpful here either. There was also no lecture on it. At the end of the semester you just had to explain how to develop drivers for an unknown OS in a programming language that most of them couldn’t before. The activities of the software engineer, i.e. setting up projects that implement toolchain, tests and their documentation, were also included. We chewed networks down to the signal level, I set up Linux gateways, set up servers and so on, just as I wrote GUI applications and database applications or controlled real machines by software. We had plenty of math lectures, for two semesters even two different math lectures in parallel, each with plenty of hours.
The most important difference from the IT specialist, however, is the fact that it is a course of study (at least in my time, I was still studying for a diploma).The project is studying and learning, researching, documenting, etc. learn from computer science topics.
In the university, the education is more theoretical.For this, the theory is more far-reaching. More math, does theoretical computer science, but also less practice.
As a rule, fields of activity mix when supervisors are interested in the interest of their employees and promote and use them accordingly.A sharp demarcation makes virtually no sense. Anyone who develops new fields of activity must acquire the appropriate knowledge. As an IT specialist, you come from a very practical corner and have to learn theory, whereas a university graduate may be able to create complex algorithms, but unfortunately cannot program meaningfully. Thus, the FIAE helps the university graduate to carve out a program from it and the FH graduate stands in between and realizes that the theorist does not consider that a computer only simulates counting and has solved its problem mathematically correctly, but unfortunately the computer inaccuracies and the FIAE has never had anything to do with it.
Example from practice: A software should be secured against unauthorized access, accordingly a password query was implemented by a computer scientist.He casually showed me this, I installed software to read the network traffic, read out the password, which he chased over the network unencrypted and had access with it.
Each level of education has a different approach and approach.At that time, I deliberately concentrated on studying at the FH, because as a middleman I was floating between the worlds.
But in the end developed most software.
The computer scientist is usually given a perspective on the computer, but should also have noticed during his studies that computer science is not limited to computers.So I would teach computer science in the sports hall again and again. After all, it is not about computers, it is about information. The word information means exclusion of chaos. For example, a Roman legionnaire has the information that an ally is next door because he is in formation. And the question of how to turn chaos into formation so that information is created can be made much clearer by turning off the computer. On Youtube, for example, there are videos where people dance algorithms – and no, this is not about Waldorf schools. 😉
Computer science is not just computer.As an information scientist (aka informatiker) you should have more on it than just programming.
They need to know for themselves whether people will stop at their level of knowledge at the end of their education.That would be a mistake, however. The job title itself is only the point from which you start your career. From then on, an untrained hobby programmer can develop in such a way that he puts a university graduate in his pocket, just as a university graduate can lose his knowledge because he does not apply it.
My degree was in 2005.As far as mobile phones were concerned, WAP (Wireless Application Protocol 鈥?Wikipedia) was the big thing, which I quite skilfully ignored, because I thought it was meaningless.The iPhone wasn’t invented yet, I was the proud owner of a Walkman handiwith with Symbian-based Internet access. The very hot shit. All the knowledge that was acquired at that time is worthless today.
I focused on system programming.This is not matter if I have a computer, a smartphone or a video recorder… Forgiveness… Dvd… Uh… Hard Drive Receiver 😉 programming. There is also knowledge that is not so quickly outdated.
After 20 years, the degree doesn’t say much anymore, it’s much more likely to ask what you’ve been so busy with in recent years.Whoever is top today can be flop tomorrow. If you don’t learn constantly, you’ll slip down, no matter what training you started with. Those who learn constantly work their way up.