How to start learning software development?

First of all, when learning software development, you can choose to buy relevant books, of course, if we want to learn the professional knowledge of software development, it must be inseparable from reading books, starting with introductory books, it is recommended to read at least four or five times.

Secondly, we can also choose to learn software development, for beginners who have just started and have not yet been exposed to programming language learning, we choose to watch some networks**, software development tutorials**, which can be more direct, easier to understand, and easier to grasp the relevant key points and knowledge.

Finally, after some tossing, if you can still persevere, then you can go to a professional software school to study, so that the efficiency will be higher.

First of all, we need to determine a learning direction, and the content that needs to be learned in different directions is also different, and the learning time is also different. For beginners with zero foundation, in the process of learning software development, there are two problems that need to be solved, one is to have an effective communication channel, and the other is to have a certain practice scenario.

Generally speaking, there are three major directions that can be considered for learning software development: First: web development.

At present, the market size of web development is still very large, and there are many programmers engaged in web development.

Web development is usually divided into front-end development and back-end development, at present, driven by cloud computing, the boundary between the front and back end is gradually blurred, and the web full-stack programmer will be a relatively large development trend, so if you want to learn web development, you should pay equal attention to the front and back end. Usually, web development takes 3 to 6 months to get started.

About learning software development, you can go to AAA to learn about it, AAA has a 200+ teaching team, layers of screening of more than 5 years of practical research and development experience lecturers, real-time revision of the syllabus, technical strength of the teaching, focusing on cultivating students' programming thinking. 14 years of face-to-face experience, 14 years of face-to-face experience summary, we have a wealth of face-to-face experience, 10+ high-quality courses and high-paying employment courses and 30+ enterprise real project case research and development to help you succeed in high-paying employment.

Self-study steps of software development: Self-learners need to understand the process of software development before purchasing relevant books and online courses. Since software development involves a lot of professional knowledge, such as software requirements analysis, module design, coding and debugging, etc., learners need some guidance, and it is recommended that self-learners purchase relevant online courses.

Many industries that value software development as a high-paying job want to change careers to do software development. However, software development is not something that can be done if you want to do it, and you have to go through a series of training to be competent, so what software development needs to learn is a hot issue that people pay attention to.

1. Software development learning should first cultivate interest.

Many people don't think about this, thinking that interest still needs to be cultivated, not at all. In fact, it is necessary to learn software development to cultivate interest, software development is a boring job, day and night in front of the computer, against **, software development engineers overtime is already very normal, if you do not cultivate interest in software development in the next study or work, you are likely to give up, halfway, interest is the motivation for you to persevere.

2. The foundation of software development is very important.

Only by laying a good foundation can you learn software development well, just like a big tree can grow into a towering tree when it has its roots. Therefore, the foundation is the foundation, without the foundation is not good to learn software development, without the foundation in the back of the learning is not carried out, if you don't understand it, it is in vain, so the foundation is very important.

3. The theoretical knowledge and practice of software development should be carried out simultaneously.

Learning software development is not only to read books and listen to teachers' lectures can be learned, but also to practice, practice is also an important learning method to learn software development. Only by making the program run can we know where your bottlenecks are and where your mistakes are, and correct and summarize them, so that we can make progress.

4. In-depth study of software development and cultivation of master realm.

After a period of study, you have fully mastered the basics of software development and some simple programming, and you can learn some software development skills and techniques in depth.

The ways to learn software development are: 1. Start self-learning software programming courses; 2. Familiar with algorithms and data structures; 3. Learning of additional skills; 4. Cultivation of hands-on ability. (1) Start self-study software programming courses:

There are many different types of programming languages, and each one has its own merits, so you need to know which one you want to learn before you learn. After the determination, it is necessary to make a reasonable study plan and implement the study plan consistently. Develop good study habits during the study process.

Software development is all about: requirements, design, programming, and testing!

Requirements: Not only user needs, but all requirements encountered in development. For example, you first need to know what problem you are doing this project to solve. What data should be entered in the test case......In order to get a clear picture of these requirements, you often have to communicate with customers, project managers, etc.

Design: Before coding, there must be a plan that tells you what you want to do, what the structure will be, etc. You have to follow this, or it could be a mess.

Programming: If by project deadline, your program doesn't work up or meets the client's requirements, you won't get paid.

Testing: The purpose is to let you know when it's done. If you're smart, you should write the test first so you know if you've actually done it. Otherwise, you often don't know which features are really done and how far from the desired goal is.

In software development, both customers and developers have their own basic rights and obligations.

Customer: Define the business priorities of each user's needs;

Develop an overall plan, including how much to invest, how long it will take, and what it will achieve;

Every working week in the project development process can make the investment get the most slippery and large returns;

Accurately grasp the progress of the project by repeatedly running the functional tests you specify;

Ability to change requirements, features, or priorities at any time while avoiding costly reinvestments; Able to adjust the project plan in a timely manner according to various changes;

Ability to cancel projects at any time; When a project is cancelled, the previous development work is not a pile of garbage, the developed features are in order, and the work in progress or unfinished should not be difficult to pick up.

If you can't think of it, then let's write first, why do you want to learn software development, and what do you use it for?

Are you involved in software development?

So what industry is software development in which industry? Banking, Internet industry, mobile Internet industry, communication industry, enterprise software ......The requirements are somewhat different for each industry.

If you don't know where your destination is, it's hard for others to give good advice, or you'll get lots and lots of advice without knowing how to make trade-offs and judgments.

Yes: 1. Think about what you want to do, for example, after 3 years (if it's too long, look at 1 year), what kind of state do you expect yourself to achieve? For example, can you get into the BAT for a developer with a medium salary, or mix in a senior developer in a small company?

2. You can first search for what requirements are needed to achieve this goal, in fact, it is very simple, search for the recruitment requirements of these companies or positions, and you will probably understand. However, it should be noted that in general, in order to reduce the pressure of screening resumes when recruiting, the general recruitment requirements are relatively complete or high, so you don't have to mind too much, just pay attention to what requirements are in them.

3. Have a general idea of these requirements or skill levels, how much time and money it will take to achieve them, and how difficult it will be.

4. If you feel the previous information almost, it's time to come out and ask the masters, ask everyone, if you start from these angles, if you want to achieve your goals in 3 years (or 1 year), is it a reasonable expectation, and then adjust your plan or expectation according to everyone's feedback.

5. According to the plan that has been compared to a bit of a spectrum, search or ask the masters, whether there is a learning experience that can be shared, not to copy a shortcut (technical things, there is no shortcut to copy), but to avoid detours.

Of course, all learning is not as fast and good as working with a master, but there is one point, since people are masters, why should they work with you? If you can figure this out, it's pretty much it.

1. First of all, if you can, it is not recommended to learn alone, and if you have money, you still have to sign up for a training class. It can be much faster with a teacher's guidance.

3. Look around to see if there are any colleagues or friends who are doing development, and ask them to give you advice. Asking them to tell you what to focus on can be more efficient.

5. In the process of self-study, you should do more hands, and follow the case by yourself.

6. Make a study schedule for yourself, and develop a good habit of studying at the specified time every day.

7. Cultivate your interest in software development, and interest is the best teacher. With interest, all learning will become active and will play a role in getting twice the result with half the effort.

1. Foundation. This is the starting point for every developer. The developer has just learned a language, such as C, learned basic data structures and algorithms, and consolidated the knowledge with some exercises.

These exercises are mainly after-class exercises, which are exercises on simple basic concepts such as printouts, receiving user input, traversing arrays, sorting, or linked lists.

The next step is to do some simple projects, which do not have complex algorithms and advanced domain knowledge, such as statistical analysis of data, after-sales management system of production chain products, etc. These projects, although simple, are a real and complete project. It not only practiced the developer's ability to apply the language, but also experienced the whole life cycle of software development, that is, software engineering, from project demand analysis, to design and development, to software release and project acceptance, and finally to software maintenance.

Through simple projects, I mastered the ability to navigate the language and became familiar with software engineering. As your ability improves, you will gradually get in touch with more complex projects, so that your ability can be further consolidated and improved.

Competence enhancement includes proficiency in the use of language and software design. Exposure to and familiarity with more languages, such as dynamic language pyhton, scripting language bash, emerging language golang, swift, etc.

Through the comparison between languages, we can have a clear understanding of the advantages and disadvantages of languages, so as to choose a reasonable language in the project.

2. Architecture design and system analysis.

As more and more projects are done, you will find that most of them are duplicating and reach a bottleneck. It is possible to read a lot of books and make the transition to software architecture and systems analysis. When designing software, pay more attention to the architectural design.

Software architecture can be derived through evolution. But if you can see farther and do some design in advance, you will get twice the result with half the effort.

At this stage, it can take a lot of time to spend in the business area. Because software technology doesn't need to invest much energy for the time being, there is also time to focus on the business area. Familiar with the business field, able to analyze the needs and constraints of users, write information system requirements specifications, formulate project development plans, etc., and be able to evaluate and select appropriate development methods and tools according to the actual working environment; Able to write system analysis, design documents, etc. in accordance with standard specifications.

Exercise system architecture and system analysis skills in real-world projects.

Software development process: The software development process is the general process of software design ideas and methods, including the first demand analysis of the software, the design of the software function and the implementation of the algorithm and method, the overall structure design of the software and the module design, coding and debugging, program joint debugging and testing, as well as writing, submission of a series of operations to meet customer needs and solve customer problems, if there is a higher demand, the software needs to be maintained, upgraded, scrapped.

The initial stage is a stage of rapid expansion of its own breadth, you can make full use of the time to learn in your work, and you must expand and understand the new technologies and new terms you are exposed to, you don't need to know very deeply, but you must know the general concept, and you will form your own knowledge system to build a good infrastructure. When learning a new technology, the information on the official website should be put first. The official website information is almost the best reference material, and most of the information shared by the gods on the Internet is translated from the documents on the official website.

You can quickly learn the basic skills of technology. If you want to go deeper, you can choose to add a lot of technology-related QQ groups or WeChat groups or communities, where you can see what problems others have encountered, and you can quickly improve your ability to solve problems. After all, the application scenarios of each project are limited, and if most of the problems in the group or community can be solved, the technical strength will be rapidly improved, and this can only reach the middle level.

If you want to improve again, you can take a look at github of the new technology, the wiki in github will have incurable diseases that cannot be solved by various gods, and the official people will also answer various questions. Of course, you can also pay attention to stackflow, the problems recorded on stackflow are also more difficult, and there will be many solutions above.

Medium-term: In the mid-term, you can choose one or two components to learn, and you can learn the best writing techniques in them. When writing, you must pay attention to the naming of methods and variables, and these small writing skills can be learned from the source code.

After all, most of the people who can write open source components are gods that we can't reach, and there are so many things we can learn, whether it's the use of design patterns or a lot of technical writing ideas.

Anaphase. Later, when choosing your own natal components, you must not fall into the details at the beginning, if you fall into the details, you will learn and understand it in the short term, and forget it after a while, you must understand the big structure or data flow, and then gradually understand the details after you have a general framework in your mind.

Long-term. To be exposed to learning some ideas, such as first principles, competency models, note-taking structures, etc., everything is routine, such as writing articles, considering problems, and so on. Many philosophical ideas are of great help to design and work, and enhance the breadth of our thoughts.