preface
The programmer industry is very mobile, every new company, the work is completely new.
It doesn’t matter if you’re fresh out of college. If you have more than three years of work experience, it’s not going to take you a long time to get familiar with the program.
Only in the shortest time, quickly understand the project, quickly start.
Next, kaka will use his own experience to talk about how to get started quickly after entering a job.
First, formal work
On the first day, according to the Offer entry time, report to the personnel and complete the entry procedures.
When you have completed the entry process, hr will take you to your station, at which point your position has been confirmed, and the next step is to officially start work.
You’ll need to download everything you need to do your job, and Kaka suggests you sign up for a Google account and save everything you use in a TAB.
This way, when changing computers or jobs, you can directly log into your Google account and synchronize your bookmarks, so you can quickly complete all the preliminary work.
Then go to your team leader or supervisor to develop data, development data is nothing more than interface documents, database information, code base, code specification, build table specification these several kinds of development needs these data also go.
After you get the data, pull the code down first and run the project according to the documentation. If the project has any problems during the operation, you need to record them, because you can’t only deploy this one time, and record them for later review.
If you can’t get the project going at all, don’t mess with it yourself, and find someone in your group to help. Don’t ask because you don’t know how to do it. Not afraid of work problems, but afraid of you.
Try to get the project running on your site on day one, and do simple debugging.
One more thing to do when you get home from work is to build a new project at home in case you need it. You know, bugs don’t show up when you’re in the office.
Just solve the following problems on day one.
- Configuring the Local Environment
- Request development materials from superior leaders
- Run and debug the project locally
Consider what to do rather than how to do it
If you think about working at your last company, what do you need to know before you start writing on a new project?
Most people respond to technology, as development, of course, technology is the first, so one plunders into the code, and then, the code implementation process.
This approach is not recommended and the technical aspects are certainly understood, but it should not be done the next day.
As technology is a bug a bug to change over, in the mind has been imperceptibly. There’s always the question of how to do it, but we need to understand what to do first.
What to do is best explained by the product, and all business is built into the product.
Find the product and get the r&d schedule. Therefore, the highest priority is business. Understanding both the business and the technology is essential when you enter a new company.
Why do I need you first? Imagine if you had to read the code first and then push a business. Would you struggle?
However, when you understand the business, you can deduce the basic code framework. For this reason, many companies offer orientation sessions to familiarize you with the program’s operations.
And a product is a collaborative effort, so it’s important to look at how other members of the team work together to see what’s going on.
Often, you won’t be assigned a job in the first few days of your new job. This time is for you to fully understand the project and the work of each department.
Therefore, do not spend these days paddling. Once you’re paddling, you have no idea when it comes to scheduling your projects. You have no idea what to do. This leads to a bad mentality and makes it more and more difficult to integrate into the new environment.
Three, get the database should do
Come in constantly contact with two new items, although one is the Phalcpn framework and the other is native. It’s not the code that scares me, it’s the database.
Most of the projects received are previously developed, and the current work is either optimization or maintenance.
It is no exaggeration to say that Kaka has seen more than 2500 tables on a project, by far the most tables he has seen on a project.
In this project, multi-database connection was carried out, and 2500 tables were stored separately in 3 databases. The tables themselves were very troublesome, which was divided into three.
So if you modify a project like this, it’s probably five or six lines of code, and it takes a long time to find the table.
To get to the point, suppose you have a project database that looks like this.
The structure of this table is familiar. This is the system table for MySQL, just for demonstration.
If your project database looks like this, you need to think about whether you did too many bad things in your past life.
If the situation is like the one above, no one can help but work overtime.
However, if you annotate all the tables and fields in the database, it will be much easier for the next person to take over the project.
Execute MySQL query
select
TABLE_NAME,
TABLE_COMMENT
from
INFORMATION_SCHEMA.Tables
where
table_schema = 'enen''
Copy the code
It is clear what each table does from the above picture! The usual database design is associated with project modules.
If there is a difference, it is not too big, so it is ok to find the data table according to the module.
If you take on a new project, wouldn’t you be happy to have such a database?
Therefore, during the daily development process, it’s time to give comments. Don’t spare a few seconds for yourself to read or for someone else to read.
After sorting out all the notes of the table, probably take a look at what means not to deliberately remember, start to do a few days of business is familiar with almost.
When writing business is essential to view the table notes, view the table notes in many ways, click to introduce several.
The first way is directly in the client view, very convenient
Of course, you can also use SQL to view.
selectCOLUMN_NAME Specifies the field name, column_COMMENT specifies the field description, and column_type specifies the field typefrom information_schema.columns
where table_schema = 'enen'
and table_name = 'fa_admin' ;
Copy the code
You can then copy the field comments from the table to create your own database dictionary for later development.
Start with some simple features
Usually by day 4, your team leader will have assigned you some simple tasks, by which time you should be excited to finally get to work on the project.
Once you get the assigned tasks, you simply go through them in the project, and then write an implementation document for each task during development.
The initial documentation can be the title, requirements, the path to the corresponding code file, the required tables, and field comments. Once you have all this in place, don’t rush into development. So what do you do?
First find the product requirements, your understanding of the task and product docking again, to ensure the correct development, this communication cost is very small, a few minutes to solve the matter.
Each position in the company has its own job to do, so don’t go directly to the product after receiving the demand, you need to have a certain understanding of the demand before looking for product docking. Only in this way can you guarantee the quality of your work.
What happens when you get stuck developing something?
At this point, be sure to ask your team leader or supervisor for help, and be sure to describe the entire requirement and the problem you’re stuck with, as long as it saves everyone time.
Don’t mess around and delay the project. Maybe you can ask others to solve the problem in a few minutes, and it will take a long time to do it yourself. Do not have, asked others will show their own food mentality, since you can get the offer, so your ability can be qualified for the job, otherwise, you in the interview round you are finished.
Five, how to continue to advance in a new company
In the technology group, we can see that many friends left their jobs because they could not get promoted in the original company. Some friends really reached the ceiling, while others omitted…. here , oneself experience ha!!
Don’t complain about how many needs are allocated to you in a week. The more you allocate, the more you learn about the project. As long as you keep this mindset, you won’t fail to advance at any company.
It is often said in the industry that in a small company, your technology will improve very quickly, because you have to do everything, and if you don’t, you have to learn quickly. Once you learn it, you can directly apply it to the project, so that the technology will improve very quickly. But if you’re on a team with a little more developers, you’re definitely not going to feel a significant improvement just by doing what you do.
After you assign a requirement, you should look at the business associated with the requirement and think about how you would write it if you were developing it. If the development idea is different, you can think about why others would write so, there must be other people’s reason, and then chew on what others have written, until the two pulse is open.
After a while, you’ll find yourself very familiar with the whole project. When you encounter a bug online, you can quickly locate the problem.
The above is only a personal view, according to the situation to dingha!
If you are familiar with the company’s projects, you need to start to improve yourself. Your skill level will soon show up at work. Be sure to recharge your batteries regularly.
Insist on learning, insist on writing, insist on sharing is the belief that Kaka has held since she started her career. I hope the article in the huge Internet can bring you a little help, I am kaka, see you next time.