It recruited nearly 2 years experience in a software outsourcing company, to share a little experience to the next record reviewed. (Node Time: newly recruited Division +2 Weeks)
1 are first started feeling very happy, after all, and on the job, compared with income improved to some extent. But also a greater understanding of the circle chiefs, larger platform, divided finer.
Item 2 is also in contact more difficult, as long as the understanding of the relative nature javade usage may be easier to understand business needs.
3 After the entry job status easily ----> Focus ----> nervous ------> anxiety
4 project is springboot project, compared done before, like the relationship between brother and uncle: brother mean you know his brother attributes (personality, age, hobbies, ability), you just know that he is the uncle uncle (other ignorant);
5 the first week of a few simple changes in functional parameter setting arrangement (effect of changing the presentation) can be easily resolved. Count just getting started. At the same time you get three entry exam (nice not very easy, suspect character)
6 to keep overtime, familiar with the project is very time-consuming (especially living in the middle of a group of chiefs, asking questions can not be very direct way).
7 business logic alone understand the project very difficult, rewrite the implementation of a impl did not get to know why, Hengda pressure. 200 + lines of code, add files to achieve 50+, verification, screening, judgment, groping traditional values still difficult
Big brother 8 is arranged a write task A common excuse is provided a url + + token request parameters and postman tool and realization of logic and implementation explained pseudo-code, a simple realization. The next day is a rewrite of the original method B calls A data acquisition front-end return (to achieve class method must be changed, I tested has a problem with the postman), the difficulties encountered in the business logic at work have not straightened out, parameter passing relationship corresponding knew nothing about the project from the public way to achieve the less skilled (feeling hard top). Feel is the right way, or understand the slow progress of the project.
9 summarizes some experience and learned through Baidu
1) did not ask to ask questions, problems are arising in practice, there is no timely resolution will just continue tired (produce working pressure).
2) less ask PM, old colleagues to ask more, but I do backwards (awkward)
3) timely feedback progress (as long as the projects are the result of)
4) be familiar with each other, then one or two old people, humbly ask questions. Can quickly locate problems are experienced, encountered some (unexpected change a configuration problem, the problem in the software company's internal network can not be requested, using front-end framework do not understand, ZK has been an error of ...)
Summary: entry risk, programming need to be cautious