Click below to follow me, and then click... "Set as star" in the upper right corner to receive updates as soon as possible~~~
This section will share with you how programmers can quickly get started with projects from the three aspects of "Tao, Technique, and Tool".
1
road
Tao is the principle and law. Everything has a Tao, and software development also has a Tao.
The essence of software development is to convert clear business requirements into reliable system implementation, which is to convert things in real life into objects in the program, establish data models based on business objects, and formulate program processes and rules based on business processes and logic. , through one or several programming languages, combined with some unique software systems in the form of middleware, so that the software system can achieve the company's business goals.
There is a popular saying on the Internet right now: "Interviews build rockets, work turns screws." Everyone is complaining that you are overqualified and think your work is simple. In fact, it means that what you do is just repetitive work. You face business logic every day, add, delete, modify and check. Everyone is tired of doing it over and over again. From this perspective, it can also be seen that after everyone has been in the industry for a long time, they will think that software development is just adding, deleting, modifying and checking.
In fact, no matter which company they are in, no matter what technology they use, after programmers come in, they will add, delete, modify, and check the company's business needs. This is the basic operation of data, and call them through interfaces according to business processes and logic, so that different business modules can proceed. Data communication to achieve the purpose of realizing business needs.
As business develops, the system will become more complex, and people will optimize the architecture to decouple the system, build components and services, continuously optimize system performance, and enhance the system's availability, reliability, and ease of use.
You can also use a formula to define the essence of a program: program = data + algorithm. The algorithm here can be understood as business logic, processes and rules, and all software technologies other than data.
No matter how complex the system is, it is actually a combination of data and business logic, and some technical means are used to solve the problems encountered in the system.
1. Data level
SQL database: MySQL, Oracle
nosql database: Redis, MongoDB, Memcache
Cache: local memory, distributed cache
File: ftp
2. Algorithm level
Front-end technologies: HTML, CSS, JavaScript, jQuery, ajax
Java technology: Java basics, J2EE, multi-threading, JVM tuning
Java framework technology: Spring, SpringMVC, Struts2, Hibernate, Mybatis
System interaction: HTTP, HTTPS, WebService, Socket, XML, json
Server: Linux, tomcat
Internet technology: microservices, message queue, distributed
System architecture: design pattern, high concurrency, high availability
No matter which company you are in, the essence of software development is the above things. Whether you are a newbie in the workplace or someone who changes jobs, if you master these, you will master the way of software development.
2
technique
After mastering the way of software development, it is definitely not a problem to get started with a project, but it is not necessarily possible to get started with a project quickly. The focus of getting started quickly is speed and efficiency, so getting started quickly must have its own ways and methods, which is what we say here technique.
Here I would like to share with you the four key techniques I have summarized to quickly get started with a project, as shown below:
Now let’s talk about what it means to develop the Four Essential Techniques.
1. Code
Get code
As technical developers, our job is to write code, so when we arrive at a new company, getting code is our priority.
Different companies have different processes after joining. Some companies will give you the code directly after joining, while some companies have more complete processes and need to go through the permission allocation process, onboarding guidance and so on. No matter what the situation is, when we arrive at the company, we want to get started with the project quickly, and the first thing we need to do is get the code.
If you have been in the company for a few days and have not yet obtained the code permission, what you should do at this time is to find a way to obtain the code.
Provide some ideas: ask your leader for it. If that doesn’t work, ask your colleagues to copy it. You can fight for it with a positive attitude. Don’t be afraid of being criticized. There will always be someone willing to provide you with what you want.
After getting the code, if you are given an account and permissions, you can use the version management tool to import it into your development tool. If you copied it from a colleague, you can copy it to your workspace and import it into your development tool. in the development tools.
Research code
After getting the code, the next thing we need to do is to study the code and figure out the structure and style of the code.
At this time, do not directly open a code file and read it from the beginning. This will definitely not work. The first thing we need to do is to understand how the code project is layered and how many modules it is divided into. This is mainly judged by the package structure of the code. Generally speaking, there are business packages, public packages, basic tool packages, constant packages, data structure packages, etc.
The next thing to look at is the resource package, which generally contains various configuration files. Through these configuration files, we can determine what framework and technology the code uses.
Next, find a seemingly simple business from the business package, such as data query. The keywords are usually get, query, search, etc. Start with a simple business, look at the relevant code, and combine the comments of the code , quickly understand the style and technical details of code implementation.
run code
After the above code research, we will basically have a basic understanding of code engineering. The next step is to let the code run. You can refer to a business code, simulate a requirement yourself, and use a similar coding style to implement this requirement. The purpose is In order to quickly adapt to the development technology and habits of the new company.
Here, if you encounter an error in the code and it cannot run, don’t cover your head to solve it yourself. When you encounter a problem, immediately ask your colleagues around you to help solve it. Don’t worry about whether others think you are incompetent. This is not the point, because it is possible in every company. Use your own unique technology, and also have some small unknown configurations or technical points. Asking old colleagues to help solve and remember these details will greatly increase your efficiency.
Remember there is no need to waste time getting the code to work.
2. Data
Data mainly refers to the database, because the data in the system is generally stored persistently in the database.
Get database
Some companies' databases are maintained by operation and maintenance personnel, and some companies are maintained by technical personnel. However, no matter who maintains the database, generally the permissions of the production database will not be provided.
Therefore, obtaining the database here can be understood as obtaining permissions for the test database, or as a read-only user for the production database.
research database
After obtaining the database, the first thing we need to do is to understand the system's data model, table structure and data storage format.
Here we will introduce it to you from Oracle and MySQL respectively, and understand the database model through key tables and instructions.
Through the above method, we can quickly understand the database model, including how many tables there are, what columns are in the tables, and query the data in the tables. By combining these data with the code, we can basically quickly understand a system.
Oracle
USER_TABLES can query all tables of the current user:
SELECT * FROM USER_TABLES；USER_TAB_COLUMNS can query the columns in the table:
SELECT * FROM USER_TAB_COLUMNS;MySQL
Display the names of all tables in the current database:
SHOW TABLES;Display the fields of a table:
desc 表名;SQL
Query a specific table:
SELECT * FROM 表名
3. Documentation
Collect documents
Generally, after joining, onboarding materials will be sent to everyone, which may contain technical documents, or some of the company's development specifications or employee rules.
If there are no technical documents, at this time, you can go to your colleagues around you to find out whether the company has a database, whether you have thought about the requirements and technical documents, and if so, you can ask for some.
Documents are generally divided into development specifications, technical information, requirements documents, design documents, database documents, test cases, deployment documents, etc.
Read the documentation
There may be a lot of documents, and reading them one by one is a waste of time. Therefore, I suggest that the first thing you read is the development specifications, which may include the company's development process. Through this, you can quickly understand the project's development process and what needs to be followed. standards to prevent errors in the work.
Another thing everyone should read is the requirements documents and design documents. Through the requirements documents and design documents combined with the code, you can quickly understand the project, so that you can quickly get started with the project.
Finally, use your spare time to read other documents you find useful to learn more details about the company and project.
4. Business
The business part will be explained in detail in the next section "As a newcomer, how to quickly understand the company's business" and will not be repeated here.
3
device
Utensils here refer to tools. "If a worker wants to do his job well, he must first sharpen his tools." To get started with the project quickly, you will definitely need some good tools.
Here we introduce to you some tools commonly used in development to improve development efficiency.
IDE: IntelliJ IDEA, Eclipse, Sublime
Notepad tools: UltraEdit, Editplus
Source code management build tools: TortoiseSVN, Git, maven
Database tools: PLSQL Developer, navicat, SQLyog
Design tools: PowerDesigner, Visio, XMind
Other tools: Xshell, Xftp, BeyondCompare, JMeter, Postman
Proficient use of various tools, especially the various shortcut keys of IDE, can greatly improve the efficiency of work. There is a lot of information on the Internet about the skills of using the above tools, and you can learn about it.
Next, I will introduce to you how to quickly understand the company's business as a newcomer.