Shulou(Shulou.com)06/03 Report--

I have been engaged in embedded development for ten years, and I have some feelings to write. On the one hand, I urge myself to see my own shortcomings and recognize the direction of development in the future. On the other hand, I know very well that many friends will worry about not knowing what knowledge to store as I did at the beginning. So write something to provide reference for these friends. Some superficial opinions. Friends who feel helpful or still confused here can keep penguins.

First of all, IT is an industry that needs to keep learning, and no other industry needs to keep in touch with new things and learn new knowledge like us, as roared in "you can't afford to learn computers", engage in upper-level development, all kinds of programming languages; engage in system development, all kinds of systems; do the bottom, all kinds of assemblers, chips, instruction sets Of course, no matter what layer you do, you can do all kinds of compilers, tools, hardware and software knowledge, and so on. A small part of any kind of knowledge is a pile of brick books.

Second, the embedded industry is more like IT in IT. Lack of standards, changeable specifications, and rapid technological change, the newly popular technology may lose its vitality in less than two years. For example, Symbian, Nokia gave up, iso, there is no movement, now Android is very hot, maybe in a few years like today's Symbian, it feels like never keeping up with the pace of the times.

Therefore, many people say that IT is to eat the rice of youth, it is not too much, when you get older, maybe the technology will be inadequate. Especially in China, the status of technicians. You know.

What kind of technical talents does embedded industry need?

Take a closer look at the job requirements of all kinds of recruitment, nothing more than

1, general requirements: such as what education, how many years of work experience, innovative spirit, strong ability to work under pressure, hard-working, good at communication, serious attitude and so on.

2, professional requirements: this is really a lot, but nothing more than all kinds of proficiency. Proficient in control theory, circuit design, various hardware driver development, linux kernel and tailoring, C/C++/Java language, DSP, ARM, linux/ecos/ucos/wince/VxWorks, embedded database, multithreaded programming, various network protocols, bus protocols, Symbian / Android / IOS platform application development, assembler, compiler Binary tool Proficient in various media encapsulation formats, coding and decoding; proficient in communication technology; proficient in hardware schematics; proficient in PCB design; proficient in computer structure; proficient in bootloader, proficient in... I feel that as long as you are in the industry, you have to be proficient.

After reading all this, especially the professional requirements, you have a big head, right?

There are also some skills that can be used in all four categories:

1. Basic skills: engage in embedded development, as well as some essential basic skills.

2. Special skills: essential for some parts of embedded development, but not very useful for some (such as application development).

3, the ability to expand, these may be needed.

A) Communication protocols, for non-application layer communication protocols, I really do not know whether to put it into the category of the operating system, because many operating systems do not have a network part, but in many ways it is provided by the operating system. Of course, these lower-level communication protocols don't seem to care much, because there are too many open source protocol stacks. Application layer network protocols may be concerned about, such as http,ftp,rtsp,rtmp,mms and so on.

B) Audio and video processing, such as file encapsulation, audio and video codec, various audio and video standards, and streaming media. Ffmpeg is a good thing, so I suggest you learn it.

C) Information security, well, this area seems to be getting more and more attention now.

D) Database, alas, the ability of embedded devices is getting stronger and stronger! I don't think there's any need to cross-compile any more.

Sometimes I discuss the current needs of the industry with my colleagues, saying that companies are always unable to recruit people, and programmers always say that they can't find a job, so they have a lot of feelings. Is the company demanding, or is the programmer demanding? Sometimes when I see some job requirements for recruitment, it always hits my confidence. I count them one by one, as if there is really not much I can do, so I have to work harder and harder. Of course, sometimes I feel that some recruitment is unreliable. If I look at the requirements, I feel that if all the requirements are met, ordinary people will have to work hard for ten or eight years. Such Daniel probably does not like the salary given.

It is really tiring and difficult for programmers to do technical work. Search the Internet and find complaint posts and emotional posts everywhere, which fully reflect the physical and emotional test of this profession. If you are not afraid of hardship and want to keep the technology going, then work hard. Maybe one day you will pick up a job advertisement and despise it: "Fuck!" that's all you ask, you'll drop the price if you go! " Then you are the real Daniel! At that time, you will appreciate what you have done now. If you are still at a loss, you can leave the penguins here. I believe I can help you climb another tall building.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.