The company's departure from B feelings
Company B What have I learned?
In a big company first learned is that it is more mature and perfect system management system, not just at work, or even life, the training, accident etc., a comprehensive system to deal with. Especially in a complete code development process (development, review, commissioning, controlled or changed) will greatly reduce the risk of error codes, but the lengthy development process also makes changes in the small also need a longer Development cycle.
In the Industrial large companies, its techniques are often more mature and stable (except for a few frontier with positions of research, but this is a very small number, unfortunately, I am not), make some achievements if you are seeking technical words , the probability of a large company you down too much. Mature and stable code that you almost need only minor changes that repeated several parameters, maintenance and development work is substantially equal suitability, some jobs a year down the amount of code pitiful. If you think a programmer to code the code are kept, there are many programming problems every day waiting for you to make you bad resolved, and that probably let you down. I am here for the industrial companies, the current rapid development of Internet, software, relatively speaking it in other areas of the amount of code and the number is probably the most difficult problem.
B talk about the company's treatment
In my opinion the company B belong to the same work with salary, why is it seems not directly say it? First, it does not provide salary system is based on years of service, but the fact is closely related to life and work, about the same age as long as a department (company too, as different companies, there will be big differences of large departments) differences are small. That there is the problem? Salary is not the strength of points according to their abilities, it would discourage the strong ability. The basic salary is not another two years, 17,18,19 session of the graduating students take the same wages lead to new people have left. Fortunately, however, the old staff salaries in the past have ticked up, although not really high-paying but steady work easily, so older employees are stable. So I sat in Company B of the department three years of a large number of departure, length of service in this segment fault occurs. But leaders have to brag about how much the company has more than 8 years old employees are proud to know that the real hard work overtime, the main manufacturing output is about three years young and less young people of this section, in innovation on almost lose its vitality.
B talk about the company's technology research atmosphere
Older employees are seeking stable and self-protection, to prevent accidents anxious not to make any changes to the code after the sale, even though the code written inefficient and repeat. Repeatedly raised during my old job want to improve software architecture, also increase the number of safety testing exception handling, but they refused to be stable big code changes, then I also agree with this view, stable product Industries the company should really pay attention to stability, advanced technology, then it is very minor. Industrial technology in the company to do your research focus is on the product, rather than technically! (Next explanation is that leaders hope that you include details of the product characteristics have to understand, but how high you do not need programming skills)
B's talk about relationships
Overall Company B pressure is very small, weak competition culture. Your promotion and pay rise to a complete set of rules, without the need to take leadership ass and other leading word. Therefore, the relationship between colleagues leadership is more simple and easy to place, but basically limited to colleagues in the project team and you do business inside (the company which basically are the same, except for some more activity the company, you can engage in the company cultural events or gatherings meet more people, unfortunately, my company's department B is not the case).
Some first Tucao
- Cumbersome and inflexible processes.
This may be a common problem of large companies, whether you are large or small modifications (only small modifications to the version number is no exception), you must complete the process of many steps to go again. I sometimes wonder whether you can process large projects with large and small with a small flow, rather than engage in a unified, but also make the process too kind, who is going to judge the amount of modification to calculate how big or small it. Therefore, the development process for detailed monitoring and recording, greatly reducing the accident rate, but also makes the development cycle Duan Bule. But take the platform than the paper process single process a lot faster, at least you do not have to go everywhere do not know where the leadership of the signature, B is currently such a change.
There is also a very rigid process example, I never thought that would repeal a project and process-related. Customer upgrading from a version of the old version of the program more than a routine, until I write the code, review, debugging, a report to the last step when controlled, were told that the platform does not support a version of the program flow to upgrade a multi-time version of the new program, only a version of the program to upgrade a previous version. Customer demand really need to upgrade the version more, carefully think demand is reasonable, you would say that reform process it! Then the following process is not able to change people who want to change, and change the process cycle is quite long and big impact. Finally, select only one version of the upgrade to customers, other upgrade projects are abolished. Previously difficult to imagine a repeated reminder of the urgent task because of the controlled flow reasons abolished.
First wrote here, free to continue to update, to be at work. . .