The story of programmers and project managers driving the workplace

1th Story Programmer's Office philosophy

In fact, the philosophy of the office is a bit big, let's call it first. I have been graduating for more than 10 years, my favorite thing to do is basically done, including work and life. At least not much to let me regret the things, the study also learned, the work is also working, the crazy play also crazy play. Here is my summary as a it person, for everyone in the workplace. Hope to inspire you.

1, do not always say that the current technology is not new, the framework is not good enough (have the ability to do their own, action up, do not force on the lips)

A person who lacks experience, or who has just entered the workplace or who has worked for a few years, should not easily say that the current technology is good or bad. The use of such a framework is also the core technical staff assessment discussed, is suitable for the current situation of the company (such as technical structure, human resources, historical legacy and other factors). Saying these words will have a few meanings: one is that these frameworks are not good, it proves that you have the ability to discriminate, good others will think you have the ability to build a new framework, have the ability to guide the development of technology. Second, you lack of experience or you are new, you just came to say that the structure is not good and so on is negative information, let the qualified old staff how to see you. Time is long, people will become more and more hated you, you are a Zui zi. So do not say no practice, blowing a good blow too hard easy to hurt yourself. So don't always say what new technology to use, what to redesign the system. I think, we should not be in the workplace without the basis of the disorderly evaluation framework and technology, to have a basis, to be able to land, to be able to point out the problem after the solution, not every time the mouth forced.

2, do not blindly believe that market-making people

To be a sales person or leader in a market, a technician is often more mean. They face the customer as the grandson, the face of technical staff and like to be his uncle. What the sales will instill in the technician: do as soon as possible, finish with the bonus, finish me to the company to help you apply ... Either the year-end award helps you apply for an X-month salary, or you are invited to dinner next week, but don't take it too seriously. Development work is a long-lasting thing, if you start a passion full, time has been sales grinding without passion, but the technical staff will be considered to work not before. So the passion must be maintained, or it will maintain a moderate passion. To have the ability to screen salespeople to "trick" technical staff, don't take their words too seriously.

3, guide or help colleagues work, let the other side know you are helping him.

It is a programmer, and most people have a similar rhythm and work at least 8 hours a day. Everyone has encountered problems, and everyone has given them guidance. We should be thankful for the people who help us, and don't think they should. Be aware that they also have their own development tasks, some project managers designate him to give you guidance, or you ask someone to give you guidance. But whatever the case, please be thankful.

And we sometimes give guidance to colleagues or help him solve problems. I once met a female programmer, what about people? Feel a bit of a problem with personality. At the same time looks also general but oneself also very confident oneself long is the beauty. One day she asked me a question, and when I gave him to solve the problem, the mouth began to say that is not the reason, I said the code to help you tune, and said that not the reason, the living system in front of you, your mouth is stubborn, said she will not utter a word. and other people also give him the guidance of the problem (her technical personal feeling really general) guidance is also a bunch of sissy, show their own very good appearance, Mom, and the Code of Self-tuning do not find others to help you. Later only to know that connections into the company. For such a person, to let the gorgeous euphemism refusal language mercilessly give her a big mouth. Everyone hates the people who talk nonsense, show their own. So others help us to be thankful, we help others to be patient a bit, if the other party hooves to cut him well.

4, high-profile work, low-key life

It's a simple truth. is to be modest for people, to do things to show their own positive side. I work together, often in front of the customer, the manager said that he was in which project for several months in a row to work overtime to a few times, other people are almost unable to hold the words. Overtime may be due to the need to do a bad job, it is possible that the design is not good, or the duration is tight and so on. Of course, overtime is a fact, regardless of the cause of overtime is overtime, the expression of their own to the leadership, which is called high-profile work (of course, this Buddy Express way is very straightforward, completely can be changed, such as the previous period of overtime to the night is to deal with XX problems, after careful analysis using XX method to solve the XX problem, Note: Don't say who solved it. Focus on what to solve the problem), no matter what you do, you have to tell others what you do, and your efforts to tell others, especially your boss. This is to get the team members to recognize your cool and let the project manager know where you are. Otherwise people processing capital when why to give you add, this is high-profile work. A person should be low-key, such as modest ways of doing things, irrelevant matters by the decisions of colleagues and so on.

5, do not think you are very lofty

Many programmers live in their own small world, feel very petty bourgeoisie, in the presence of small white-collar workers, one months to take the million-piece wages, superiority full. But now the money is not worth the situation has not let you really awake. Career is not a distinction, so do not consider yourself a programmer on the lofty, there is superiority, of course, there is no need to denigrate and self-black programmers, pay attention to maintain our image. When you talk to the junk for one months how much do they make, when you talk to sales people about how much you earn for one months, how much money you earn when you talk to the bank staff for one months, see if you have a sense of superiority? Of course, so much is not let us than wages, people than popular dead. In the final analysis of the meaning is to tell everyone, as a programmer to precipitate down, calm down to continue to improve their own attitude is not so lofty and superiority. It's no good for you and me, decently.

6, cherish the people around

Programmers are so busy that they often neglect the people around them. Including your father, mother, your lover. My parents ' grace is to be reported, I will not say this. As for love, I feel that if a woman can always support you silently when you do not have a career, then she is really great, it is worth you to cherish. Spend more time with her, even if accompany her to watch movies, read anything. Have time to buy some small gifts to coax. Women are not so difficult to coax, not to 30 or single Wang, of course, if you want to do. Treat their parents to be patient, do not abandon their nagging and annoying, now I am 31, I more and more quiet listening to parents nagging (one ear in, one ear out), they can make you out of the difficult. You and I are grassroots, even if mixed with a dog-like, remember to stand on the shoulders of giants (parents), benefactor grew up.

7, met the person you should help, just help. If you meet someone who is not worth helping, don't offend.

In fact, we often need a person to wake up and guide us, so when colleagues need to help them more, one is that you become more and more popular, but let everyone really understand your technical and other aspects of the ability, in the future you will be the technical manager, project manager. In addition, in the company to know as many people as possible, maintain good popularity (especially in other departments of people, many technical people do not love to talk, do not love the cross-departmental understanding of colleagues are the drawbacks), know other departments of colleagues, leadership, can help a little busy to help a little busy, so that as many colleagues know you, This way the boss can ask you and understand you from other department colleagues, and your chances are more and more. Of course there are some silly, think you help him is should, still not grateful to people, met such a person I want to say do not offend him can, to maintain distance. You know, offending a villain can ruin your big deal. So in the workplace, come on, be a positive energy person. You don't have to say hello to all people, the key occasions are more than the average person says hello is enough. Understand the move, and mix well it workplace.

2nd story My project manager growth Road

Low-key, educated general, both inside and outside the character. Yes, this is me. entered the IT field for employment ten years ago. From the original novice programmers, database developers, demand analysis personnel to grow into today's five years of experience in the project manager. In this 10 years of experience has experienced a lot of difficulties, there are career development confused, technical, have a human life and so on. In addition, I often focus on a number of forum technical stickers, career planning stickers and so on to learn to compensate for their shortcomings. Today can not restrain themselves, will their struggle process simple write to share with you. Rookie through their own efforts can also be small in the IT field. The writing is ill-conceived, please forgive us.

  I graduated from a general tertiary institution in 2006, majoring in e-commerce (partial text). Before graduation, you know the employment situation is grim (mainly lack of technology, no work experience). In the teacher and classmate's suggestion to a training organization to study six months of Java and other courses. Interview more than 10 companies to fail, after listening to the guidance of the tutor to revise the curriculum vitae (change to 1-1 years of work experience), while the interview blew the Ox x success into a company to become a rookie programmer. Now recall that the scene of his own interview with the experience of interviewing others has done some interview summary. First, if the lack of real company work experience and practical experience, the interview should be appropriate to exaggerate a bit of work experience, show no urgency, the state of self-confidence. As a junior developer, the interviewer will not ask for technical skills, understanding in depth, but the interviewer should show positive attitude, the second is to understand the network and other ways to give the written test surface questions. Only after the understanding of recitation can make the knowledge systematized, theoretical, the interviewer will feel that you have a good foundation, is to cultivate talent (recite the use of the official terminology to answer the question will appear tall, if you have a degree in general, this will appear to be a class of some). Third, if the interviewer asks you a relatively complex question if there is no specific way to say their own ideas, if there is no idea of the case, you can honestly explain about this knowledge point has not been involved in. Do not huchui nonsense, this will give people a reliable feeling.

    2009 to the second company. I was born grassroots, financial constraints or the main reason for job-hopping. At this time has two years of work experience, about the technology, and colleagues to work together to communicate and so on have accumulated a certain experience. In this company mainly do Oracle database development (during the interview, the Ox X said that he had done the clearing program of the Telecommunication Project). In fact, the database background development has not really done, helpless to learn from the beginning. First, the new field of business does not understand, the second is the background of the database development has no practical experience, three is in the probation period. For the first time during the interview, I blew the Ox x to show myself, in addition to working eight hours a day, I consciously work overtime for two consecutive months, every night to death knock study to midnight. Including the development of stored procedures, trigger development, program call Database daemon, job development and so on. Then successfully delivered three modules of the database background development to the test group. Three months later the project was successfully launched. Because of their own idea is relatively large, coupled with their regular initiative and lead colleagues to communicate, the leadership of my gradually trust. Assign more work to me. That period of time really exhausted, pay a little return. A good listening point called the leadership, on the other hand called the Squeeze Group members (a person to do three people's work). But look at yourself. I just give myself a positive psychological hint every day I can do well, I want to insist on doing well. I think of doing more work as a leader rather than squeezing my workforce. Later, I was in charge of coaching two new people, and I was a long team player. Then our department manager left, and I worked for more than two years in the seven or eight-person team. After the experience of this company I summed up a few points. First, do not worry about what you have not done, and to dare to take the initiative to undertake, development is the process of learning and practice, but also to prove that they have strong research and development capabilities; second, do not care about personal gains and losses, more pay (such as not to complete the task of self-consciously overtime, is actually the first interview blowing, haha ) has the ability and experience to improve. Third, do the procedure is relatively boring work, the development process and other work content and leadership, colleagues more communication, improve their communication skills, can not only adjust the atmosphere and can have the opportunity to do the work outside the development, four, the work of constantly die knock themselves, whether it is technology or communication to improve themselves, must be improved. To focus on communication skills, so career development will be more and more extensive.

    moved to the third company in 2012. It may also be an opportunity or a reward for your own efforts. It was the experience of working with the company that led me and the leaders to build a deeper trust. I went to the third company, the last company department manager called me and said that the project team was being formed. I, and more competitive, with nearly five years of work experience, feel that their communication ability is OK. At that time I offered to interview the project manager. At that time, he felt a little hesitant, after my active communication. From the language development, database development, active communication and other aspects and leadership negotiations he gave me this opportunity (to tell the truth is not practical with the project experience, I have concerns). I started my project manager tour and led four developers to develop a small B/s structure system. Research and development often have technical problems, some members asked me, but also I did not meet the problem, I have to think of the way to prove, but because it is a new team, often a group of people do not obey the situation, I began to write their own code to solve the problem. Experience a few times after the team members run-in more and more good, I also get members of the recognition has a certain appeal. In addition, the project manager in the development process to track progress, control time, labor costs. At one time two members of the team because of a dispute between the red, in fact, the problem-solving methods are similar. For the harmonious atmosphere of the team to appease the members of the mood, can not let emotions affect the work. Even so in the project management I still have some problems have no solution and ideas, this time to consult other colleagues, after a separate talk to ask to get the method and ideas to deal with the problem, in this also thanked the Department boss. After the process of developing the project, I summed up a few points. First, the technical team mainly to technical convincing, at least before the new colleague to have a few times to prove their own opportunities, no opportunity to create opportunities, so that members of the team will support your lead, in fact, a lot of domestic company project managers are technical managers, such as my position in this company and work content, The project manager of software development is the manager who is least like the manager. Second, the control of cost, manpower and other important elements, the company is to squeeze the labor force, the actual personnel are lack of tension (we lead that the manpower is abundant project will not make money, now want to have a little truth). Therefore, we should rationally match the manpower, allocate the module and arrange the time reasonably, and control the progress. Third, the team is composed of people, where people are more prone to problems. Regular and irregular communication with the team members to understand their real ideas and demands, the stability of the team, the atmosphere of the team to build better. Four, in the discussion of the problem should be low posture can not be imposed on their own ideas to the team members, to reasoning, but on the contrary, the company system and management should be serious, increase prestige convenient management team.

2013 to present, in the fourth company as a project manager, product Manager position, by the headhunting company recommended. Mainly led the project team nearly 20 people developed a large project and two products. I interview is the project manager's post, to the team is a new face, just at the beginning is not convinced, but also to my leadership reflects on what to recruit a new person directly as a project manager, let the elderly how to see, even have individual colleagues directly to me that you just came to the project manager, I have spent five years or intermediate developers (we have been together for three months, I would like to work 6-7 years or intermediate development, technology is not good, all day long mouth nonsense, write code will not be). Then I and he ate a meal alone, low posture and his open heart of deep communication, slowly he put low on the alert accepted me. The idea of project and product development is still a big difference. The project has been asked to investigate the specific objects, and product development has just begun the need to extend from the project, and sometimes behind closed doors, follow-up to the market confirmed. Projects often have a definite duration requirement, and product development is not necessarily. The SVN version of the project is simple, and the product often comes with multiple branches of management. After their own precipitation and the product of careful thinking research on the company's product positioning has a new understanding and recommendations, the successful development of two sets of products deployed in more than 20 provinces nationwide, during travel also more, and finally understand the bitterness of travel. Now the child is soon born, continue to kill themselves, for our better life.

After 10 years of struggle, I now grow into a little experience of the project, product manager. Project manager, in fact, in Europe and the United States IT company is team leader role, and China's project managers are in fact a lot of technical managers, and larger companies or teams to focus more on the real meaning of project management. With my present company's role is management, technology about half. But in fact, I still have a lot of shortcomings, technology and management have. Here are a few personal tips or suggestions that I have given to the project manager and my colleagues who are working as project managers to share and consult with you:

First, to have a better technical background and growth experience, death knock yourself, learning technology and management (focus on communication, coordination Learning project management of the Iron Triangle), so as to serve the team members, let team members convinced.

Second, the communication problem to put low posture, at this time can not be regarded as the project manager, to technical convincing, reasoning, remember to assume the leadership posture, but in the company system, management to be serious, management can not and everyone laughing and joking, this is not conducive to project and team members management.

Third, regular and irregular communication with members, the sense of feeling, understand the members of the real action to sum up the inner thoughts, can help them solve the problem as far as possible to help. Timely channel the heart to withstand poor colleagues, eliminate the mood, concern about special personality, more introverted colleagues, let them feel that everyone is a whole, not marginalized. Let him know that in addition to work, everyone is a colleague, you can laugh together.

Four, to the superior leadership (department manager or director of the role) regular and irregular reporting, let the leadership know our project progress and human aspects of the state, as little as possible to lead the trouble, to find ways to solve their own problems for leadership. The project manager should let the superior leadership really rest assured, take the initiative to find the leader report work results, progress. Don't wait for the leader to ask you.

Five, communication, management, etc. to decently, not anxious not impatient, showing a calm and stable state. You can not worry about the problem, team members or leaders tell you the unexpected situation when you can not panic, this will not only let the leadership of colleagues worried about your ability, more likely to be replaced. What you need to do is to be prepared for the problem and to come up with a solution when you have a problem. Technical problems have the ability to guide as far as possible, without the ability to coordinate with senior engineers, architects and other personnel to solve, communication problems to own grasp, and direct leadership to communicate, and the project team members close communication. If necessary, cross-level communication, cross-departmental communication and so on (to pay special attention to cross-level reporting, urgent need to pay attention to skills. For example, emergency needs leadership decision-making and direct leadership contact is not, at this time leapfrog instructions to advance to explain the direct contact several times contact not fine specific situation. In short, flexible treatment). My story and some of my ideas are introduced here. After 1 years of writing, I also wrote a lot of experience (content such as), need to add me v letter Aitilaowang or buckle 317507750

The story of programmers and project managers driving the workplace