Developers need to know topics for [community] author of the article: Article type very soil: human resources information article Joined: In 2003 at 19:50 on December 2nd Article Source: 21ICBBS-IC Industry Forum
In view of what many silly problems often see, such as what is used by XX languages, is the XXX language? (But it is true, these problems beginners will have.) I will talk about some things that developers should know here. But this is just to see and think on weekdays. It is inevitable that there is a deviation, please forgive me.
Software development is a comprehensive activity. Software development is not just written code. Learn to program the programming with C. The program is just the first step, one of the most basic requirements. What else else wants? In my opinion, programmers can be divided into two categories. When a job task is assigned to the programmer, a programmer knows why you want to do this. Do you know how to do this. And this The difference is big. If you know why you want to implement this, this at least shows you that you can grasp your task in the software project. If you just know how to complete him. That just means you can do this. Moreover. If you want to do it, you will not be able to do it. And the first programmer will be able to do it well. Take a look at the strips below, I hope to help everyone.
What is the key to the programming?
Programming is not a code. Quote a sentence of my friend, "Programming is a whole balance." For this explanation. "Balance, is a very important part of the software, considering programming from the horizon of balance, suppressing some ideas you want to use with the latest technology, the latest system, etc. Because from the perspective of balance, as long as your software There is a bottleneck, your program is to fail. You first have to consider how to eliminate some bottlenecks that may exist in the program. On this basis, you have the right to consider improve your program performance. "Even if you have the latest technology It is best to system if your code is not. As long as your program has performance bottlenecks, it is equal to everything.
What I want here is that the program is written. If your horizontal is not, ready-made technology is not used. Even if you use it, you may have no way to make it clear, why is this?
The second thing to say, how to program?
I think many people see this problem, they will definitely feel the body in my heart. I thought that this kid was greasy.也 也 也. I will listen to me. What I said is not to say how to write a detailed code, but your program eventually formed. I want to write here again, someone will give me a lany. But in fact, write code is a relatively small amount of time in the production process of software.
I personally feel that I have to include the following parts:
1. Market Potential Analysis Analysis Software You want to sell, or what kind of software I want to write?
2. Competitive analysis of similar products to see the advantages and disadvantages of your similar products, design your software selling points. (If there is no selling point, there is no need to continue) 3. The software design writes a detailed software process and data flow. Main algorithm. Software architecture, etc.
4. Write the code, don't say it.
5. BUG test and trial operation
6. Sell
These things, some are market things, some are what system analysts, and it is a programming. But in many small companies, I must have a principle of doing things in small companies. Everyone knows more about it will not be wrong.
For a specific example. If I want to write a shared software. What do I do?
1. Want to think about the software I want to write, there is no "money". Time is around 15 days to 30 days. During this time, you must do a good market study. This is the most critical step.
2. Ok, I have decided to write XXX software.
3. Find a few of the most threat of XXX on the Internet to analyze their excellent disadvantages. If you want them, don't have their shortcomings. Desigible to sell some software selling points.
4. According to the result of the previous analysis, the most list of the menu of XXX software should have
5. Write a 1.0 version of the basic function table to write the 1.x menu. Don't finish all the features at a time, such words, your software will never be born.
6. Select the programming language (see, the programming language is here)
7. Look online to find similar source code, algorithm. RFC standard documentation. Eat. Software code and algorithm have a good reuse of the algorithm, will make you half a meal. 8. Write the detailed design documentation of XXX based on your selected language, algorithm, standard document. Document must be used, otherwise your plan is not strong. The plan is not strong, and the random is big. The random is big, the software is very easy to fail.
9. Write code according to design documentation
10. Test and sell
Third, where is information, standard document
The world of code is a thousand variable, before starting a new project, you can find a similar function code to see. This can better improve your program. Sometimes you can speed up progress. Also when new technology comes out, you have to look at the relevant documentation. Although don't fully understand its function, benefits. But you must at least know where new technologies can be used. how to use. How other technologies can be used to play its role. Writing software is not all things you write. There are a lot of features to be a standard, perhaps the standard algorithm. Algorithm like graphics, multimedia, encrypted decryption. Some is a standard file format, like a variety of image files, multimedia files. It is also a standard agreement. Common network tools like Email, Telnet.
So you have to know where you can find the information you want. I know what I know here.
Source code and technical data site http://www.vchelp.net/ GBHTTP: //www.9cbs.net/ GBHTTP: //www.codeguru.com/ Enhttp: //www.codetools.com/ Enhttp: // Www.dexv.com/ ENMSDN.MICROSOFT.COM Enhttp://www.programmerheaven.com/ Enhttp://www.freshmeat.net/ Enhttp://www.sourceforge.net/ Enwww-900.ibm.com/developerWorks / GB Forum and Standards, Organizational http://www.linuxaid.com.cn/ GBHTTP: //www.linuxbyte.com/ GBHTTP: //www.aka.org.cn/ GBHTTP: //www.rfc.org / EN GB Various Mailist, IRC
Fourth, tools and knowledge to master
Tools can make your work more efficient and unlike.
The tool below may be used, maybe you have not used it. But there is no relationship. The old birds will teach us how to use it. (I think of which one is written. No order problem)
1. Database Tools Construction Database Tools, represents the PowerDesigner database analysis tool. Many large databases will be brought.
2. Flowchart design representative Visio 2000, SmartDraw
3. Case Tool Representative Rose
4. Code Analysis Tool Represents BounderChecker (for VC Delphi), SmartCheck (for VB) ....
5. Editor represents Vi, Vic, Ultra Edit
6. Source Code Management Representative VSS, CVS
7. Programming tool, don't tell me more
8. Others, I have not used it, but a lot of tools may be used in a certain industry. (Nonsense :))
If you know, because everyone's development is different, most people's knowledge structure is different. But there are a few things that should be the same.
1. The main new technologies in English, documentation is used as the start. If you want to learn better updates, skills. I don't know how to speak English. Don't expect someone to translate you. Generally speaking, these materials, people who understand, do not need to translate, people who don't understand have no way to translate. I don't want to look at the article that I don't understand. So most of the materials are still in the original English. Of course, there are also many people in translating these articles, but for so many information, translation is only a small part. Ask someone to ask for himself. Multi-learn English is not wrong. 2. Although the design capacity is generally, the formal company has systematic analysts to design (I guess). But 70% -80% of small companies can not be. Know how the knowledge of a software engineering knows how to use some document design tools. Or know what design documentation should be. It is also very beneficial. Compare these things if you have learned, it is your own. And these are good things. Very puzzled. :)
3. Language writing capabilities act as a programmer, most of the time is written code. But the code's annotation, various documents, test reports, documentation, and manuals, all of which require text skills. It is also useful to communicate with people, if the words are unclear, the exchange is more tongue. The level of improvement is a bit problem.
4. There are few people who have learned the ability to learn. This is not very real. The current society is not allowed to do this. It is very common while working on one side. Perhaps many people learn to make certain things among the work. Many skills are also the case. In addition, many new projects come. New technology's arrival requires us to adapt to new working environment, new work requirements. If there is no good study, it is easy to kick off a project. Ha ha. There is another point, when the boss makes you do something you won't, you will tell him, but you will get him in XX. There will be no relationship, it will learn a good performance that will be up.
5. Know what you have to do, what to learn, what to develop.
The world software technology is much like more than 9 cattle, maybe there are many. If we know everything. Oh, God, I don't want to live.
As a software personnel, it is also a beginner. I know that I am going to go in that direction. Otherwise, it is easy to starve to die in a software technology labyrinth. Finally, I have to do this. This is not very good. In general, as a software personnel, you can master the development capabilities of one to two languages. Also unless you want to do research and development of software technology (these work is the most money, you are most popular in large companies). If it is not the development of software technology, it is just a general application, and it is not necessary to pay too much about what new technology today, what new technology will come tomorrow. These things will be just known. I know that there is such a thing. It is not too late to care about the place where it is useful. I choose a direction of development and work hard. Don't be tempted by a variety of new technologies. To be honest, how many so-called new technologies is good, how is it well, many times there is business behavior inside. It will be judged by yourself. If you can't judge what to do, look at the following.
Sixth: I know more
Many initiator is the most troublesome things to choose a kind of good learning in so many software technology, and have a future (plowing), and do something that is a great thing technology to develop software to develop this unknown area. For this problem, very little understanding. If you can encounter a good teacher, that is your blessing, you must seize this opportunity. If you have to make this decision, it can only be careful. However, in general, both C and C are a nice choice. Another trouble problem with beginners is that when I choose, many of this new technology, new technologies, new technologies. what do I do. This is basically unbearable. It can only be slowly accumulating yourself slowly. It is for you to understand what these new technologies are for, these new changes are more ... These new changes are after what. You will not be afraid of these new things.
I have always insisted that if I know more, my strength will be bigger. I will not be afraid of changing. If your information is insufficient, don't make judgments for a matter of judgment. Not good for you.
Author: very soil v1.1 completion time 10:51 2002-4-22
