Are you a software engineer?
If you make a living by writing programs, then you have the opportunity to call yourself "software engineer". But it's also possible that you can't call it. As far as I am concerned, I graduated from a degree in engineering (software systems) and I am often proud to call myself that. But only after years of writing code did I understand that being an engineer is a right, not a university, but something that must be acquired. How many "software engineers" can call them the category of Archimedes, Henry Ford or Nikola Tesla? Put our eyes down a little bit, how many people can say they have been doing products for at least 10 years? or 5 years? Or is it 5 months?
Don't worry. If you have not earned the qualifications of a self-proclaimed engineer, don't worry, I believe you can do it. I think the most important thing about being a software engineer is that they (really good software engineers) are very principled and able to truly believe that they can always make progress. Through self-discipline, you understand your position and why. Perhaps more importantly, you can share it with others. When you believe that you can make progress, you will always listen to others, learn from others, and motivate yourself to become better. To achieve this, this article will be a series of sharing my principles and one of the posts I learned in previous years.
Read it! Keep checking every day you spend from the perspective of "value optimization". The programmer spends a lot of surprising time on meaningless things every day, and frankly, he is working hard. If one thing doesn't bring any value to you or your company, why spend time on it? Usually such things are meetings, parties, or "processes."
Recently, a friend of mine complained to me that since he was promoted to "team Leader", he had hardly done anything. So he decided to review his time. He found that a week later he spent a total of 20min on "engineering" alone. Now, if his other time is spent on the coaching or leadership team It's okay, but unfortunately most of the time "spends" on other people, other teams, other departments and so on.
Please do not misunderstand my point of view that cooperation and communication are totally unnecessary. I mean as an engineer, our focus is to find the best solution. This is what the engineer is going to do.
For example, if the meeting is about "syncing" (synchronizing progress between team members), then be positive. Post your progress status to a wiki, an internal blog, or a mailing list. Let the other members know your progress in time and adapt to the rhythm of everyone. If you are a team or department leader and feel that you spend a lot of time at the meeting to solve a small problem, then give it to your subordinates. This not only frees up a lot of your time, but also allows team members to accumulate more experience and grow faster. Be sure to authorize your subordinates to make some or all of your decisions, otherwise the person who solves the problem will ask you to be constantly involved. At the same time, it is important to support the decision-making of subordinates, they need confidence to make decisions, to express your opinion, do not come to this suspicion of emotion.
If your boss wants to guide "what's being done" or "What's done," it's best to find a tool to report on these things. Create a task list that is always updated, a small task that a team member can do with a little effort.
If the "process" requires you to complete the task in 5 steps, most of it is numb mechanical work. (such as generating change logs or sending email reminders), then you play your role as a "yard farmer" and try to do it automatically. Imagine a simple task that requires you to spend 10min a day. Then you spend 2 hours writing a script to simplify this task to 2min, "wasted" time only 15 days you earn back!!! Find yourself often distracted by email or instant messaging? Then turn off these apps! As programmers we need to focus on our work, and any small disturbance can mess up our process and disrupt the rhythm. One of the biggest advantages of this type of communication on a computer is "async", which means that you can communicate at any idle moment. Living in a fast-paced environment, we are very excited about the things that are unfolding in front of us and constantly moving from one task to another without thinking about why. I strongly recommend that you take a look back from time to time and ask:
How did my days die?
Am I committed to the most important or valuable thing today?
Should I be more effective in doing something else?
Finally, (I say) cherish your time, you can "develop" a better solution: use your skills to make life better!
Brotherhood high Lopheng free an apprentice: http://www.hdb.com/party/lzcw-comm.html
Free to receive the lamp brother even original PHP video tutorial CD/"Detailed PHP" Essentials Edition, details of the website customer service:
Http://www.lampbrother.net
"Brother Even it education" learn PHP, Linux, HTML5, UI, Android and other video tutorials (Courseware + notes + video)!
Web Drive Tutorial Download: Http://pan.baidu.com/s/1sjOJiAL
The above describes you are a software engineer, including aspects of the content, I hope the PHP tutorial interested in a friend helpful.
