PART ONE:
It's common to see a great idea: Do you work only to make money? No, you work for yourself, and add value to the company as you grow. That's the right career perspective, and I want everyone to remember that, so you can reflect at different career stages, am I improving? Is there anything I need to do differently? Where can I find ways to improve myself?
It all started with a discussion about whether or not we were improving during our mediocre development experience. When you've been in a job for three or five years, you have the same problem. In your first year on the job, when everything has to be learned, what you might think of as an increase is really just adjustment costs. The second year, gradually independent work, heart swelling contempt all mediocre workplace elderly; The third year, slowly become an old hand, stirring up the writing party; And the fourth year, like the third year; The fifth year, with the fourth year about...... What I want to talk about here is, after three years in the workforce, what exactly are we talking about improving?
After three years in the workplace, the business has been very familiar, maybe the telecommunications industry will be different, communication technology changes with each passing day, communication protocol changes three times a year, just familiar with the business you need to spend a lot of time, but this is no different from two years in the workplace, other simple business industry may be boring in two years; The architecture is more familiar, with more than a thousand lines of change progressing in parts every day, but the overall structure can be used for at least five years.
I don't know. Maybe that's how life is.
PART TWO:
The first part was originally to lead to the second part of the content, the result of a sigh on the writing long, once connected to appear top-heavy, had to use this form to avoid the text without proper.
The most important thing to do is to form the methodology. What I do is the performance of the company and the leader, and only the methodology is my own. Therefore, WHEN I come across a methodology or routine, I am overjoyed. Most of the work undertaken by our team is presented in the form of special topics, such as static scan alarm governance, multi-hardware multi-system differential design, interface daemon, and architecture measurement. The most difficult part of such tasks is that you don't know how to do it, and no one tells you how to end the topic. No one knows the clues, logic, and completeness of the tasks that extend from these topics, so systematic and structured thinking becomes especially important. I have recently learned such a thinking framework: Model for modeling, Realization, and Check for measuring and guarding. Different from PDCA, MRC provides a thinking framework for quality management, while MRC provides a thinking framework for creative work. Previous project thinking, I was more or less are according to the framework in the thinking, but when this refined into a general methodology, I realized that should put all project according to the framework in order, so in the past two weeks, I most of the time to do it, let me so pleased with the results of sorting.
We take componentization as an example to briefly talk about the application of MRC. The first is M. In this process, we should clearly define what componentization is, what the problem to be solved is, and what the concepts in componentization are, such as components, interfaces, states, messages and frameworks. This process should output modelized documents to guide the compilation of componentization schemes in a larger scope. The second step is R, how componentization is done, what is the result of component division, how the framework is designed, this process outputs concrete documents, this part and M process synthesis of the overall plan, the overall plan to guide the specific development; The third step, C, is that componentization should output measurable metrics, such as no calls between components, minimal coupling between components, and so on. Componentization If it is a topic, the topic is too large and will be divided into many subtopics, each of which can be expanded according to this framework.
The ability to summarize or abstract into general methods is a powerful ability.
Comments