If I write an interface to Gcc, it will still be GCC. People who have used GCC will never say that GCC is inferior to Visual C++. There is really no way to compare the two, which is not an order of magnitude. GCC is a powerful compiler, which supports N kinds of hardware platforms and official software standards, and also introduces many good features that software developers urgently need. Most excellent libraries rarely fail to compile on GCC. Hee hee, are you suspected of advertising GCC?
Regarding the commercialization of GCC, I have seen some companies selling hardware products, and their accompanying compilers are GCC or its variants. Moreover, many large-scale software can be compiled with GCC, which is not worse than Visual C++ in terms of stability. In fact, I have encountered so-called internal errors when using Visual C++, but I have never encountered such inexplicable internal error complaints when using GCC. In my opinion, GCC definitely has the potential of commercial software. Hehe, visualization is not as good as Visual C++, although GCC also has some graphic front-ends.
Opportunity comes from patience. The more patient you are, the more opportunities you will have.
Famous words, famous words, I have patience, and the opportunity comes quickly, hehe.
Let's work hard, don't really prepare for the opportunity, hehe ~ ~
If we start with MFC or VC, we will avoid many detours and make a real universal software that can be used in personal fields.
Strange, how to start with MFC or VB will take a lot of detours? Calling Win32 API from MFC or VB is very direct, especially in Visual C++ MFC. Proverbs attach great importance to the bottom. Isn't Win32 API enough? Does it have to be at the assembly level to write truly universal software? Then I'll write microcode for CPU, hehe ~ ~ ~. I use VB very little, so I won't say it. As for MFC, if you really know MFC, you will be proficient in almost all aspects of Windows (of course, I mean the user space outside the Windows kernel
Dongdong).
Whether it is hardware or software, the level of the computer is very important. An important aspect of development is to find out what level you need to do. How necessary is it for a developer who writes middleware in java to master the underlying things of the system? I think if we don't do things based on our own level, but engage in cross-level things, the result may be to contribute rather than please. It's ok to do your own research, but it's very dangerous if you don't know your level at work, hehe.
Of course, I didn't ask you not to study hard, but I think it's best to consult your seniors and make your own study plan according to your own interests. After all, people's energy is limited. Put your limited energy into serving the people, but don't waste it, hehe.
I just want to make a living and find a job. Maybe books that teach you to be an MFC master are enough for you.
I think it is necessary for every programmer to be proficient in using a certain language. Other abilities should be different for different development directions. For example, proverbs think that the second stage is to master the interface of a certain platform (such as Win32 API). But many comrades who do high-level development often don't touch these low-level APIs because there are many layers superimposed on the operating system below them. For example, programming with Java on Win32 hardly needs to deal with the system API. This actually embodies the idea of software layering: each layer is only responsible for its own functions and only communicates with its adjacent layers.
1. "The software industry will soon mature and the threshold will be higher and higher." Yes, with the development of the software industry, if you want to become a successful software enterprise, the investment is increasing and the threshold is getting higher and higher. Moreover, the software engineer industry has matured, and will eventually become a retired profession with engineers in traditional industries.
2. "Standard format is the foundation of getting started." Yes, since a programmer becomes a software engineer, he must meet the standard of "engineer". I come from an engineer's family, and I have some experience in this field. First of all, we must abide by the industry code of conduct (SOP in foreign languages). Without rules, there would be no Fiona Fang. We are a product (Mr. Liang said "software"), stability overrides everything, and quality wins. Then it must conform to industry norms, enterprise norms and production norms (that is, code norms). It is now 2 1 century, the space age has long passed, and the network age has also passed 10 years. What functions can't be done now? What everyone is competing for is not function, but performance (to see who can do it faster, higher and stronger). Secondly, as an engineer, a sense of responsibility is necessary. I won't say any more.
3. Open your mind to expand your knowledge (not the original). I think it's more important to lay a good foundation. In fact, what Mr. Liang said was basically covered when he was studying (I don't understand, many students said it was useless to learn at school), such as CPU structure (computer architecture), operating system principle and software engineering. Don't they all have courses? A martial arts practitioner can't even tie a horse stance, and he didn't press his leg. Can he only make some gestures?
4. "Half ambition is patience", hehe, this sentence is correct. Young people should not be impetuous.
5. Tell me more about the layout of this book. There is a blank "reading note" in the blank, which greatly facilitates people like me who especially like to add notes. When I was studying, I never wrote reading notes. I think this is a waste. But after work, I found that writing reading notes is a very good way to sum up experience.
The definition of a master. First of all, the term expert is amateur, and I agree with the term "expert". In addition, people who don't know much about the bottom are masters. Now a computer system is very complex, so there is the concept of stratification. As long as you become an expert at the corresponding level, you can become a master. Let's talk about Super Jieba. What is the core of his technical core? It is a coding and decoding algorithm, such as jpeg algorithm and mpeg algorithm. Who owns these cores? Mathematician, expert in image processing. These people know nothing about windows platform and debugging methods, relying on a solid mathematical foundation. Programmers just use programs to realize other people's mathematical formulas. No matter how good Mr. Liang is, he also works for jpeg algorithm proponents all his life (others have patents). Therefore, those who specialize in the industry and can debug can be called experts. Personally, I feel that only if I have a good foundation in mathematics can I become an expert (not an expert who solves problems). The higher you go, the worse your mathematical analysis ability is.