First of all, I would like to explain that foreign programmers also work overtime, they also have to meet the project, so overtime is not a reason. The real reason is that most of our domestic programmers are just tool users, do not think about the generation and principle of tools, used to an efficient tool will be enslaved by this tool; Foreign programmers, on the other hand, think about and specialize in the generation and principle of this tool, and then they may optimize 2.0 or something by themselves. And then in the middle of our lives, we moved into tool development. We moved more into management, service, and other industries.
1/ The applause belongs to someone else
In order to improve efficiency, some colleagues really fight, pull out all the best, mobilize all available resources, through programming to make a small tool. Regardless of whether this tool can improve efficiency, it is admirable to do so.
Take a closer look at this small tool, it is indeed very good, originally at least half an hour of work, after upgrading a few minutes to fix, although there are some bugs and applicable conditions. Other colleagues applauded, and the leader was also greatly appreciated. The leader wanted him to train other colleagues how to use this tool to improve their work efficiency. This tool is the crystallization of his wisdom, sweat and ability, he should be rewarded, promotion and salary increase. Yes, the story does go in that direction.
STOP! Remember that this is someone else’s success, not yours!
Can’t you, both as a melon eater and a tool user, do something other than cheer for others? Would you rather just be a booster to help others achieve their best in life? Are you willing to spend your life as a green leaf to foil this big red flower? You’re just gonna live in someone else’s shadow feeling sorry for yourself?
Don’t wait for others to win married white rich beauty, you are still in tears.
2/ Do you know the difference between reality and fantasy?
In the enterprise pay attention to efficiency, efficiency is an important embodiment of action. Therefore, all kinds of modular things came into being, putting each module together to form a powerful system, tens of thousands of screws, to ensure the efficient operation of the machine.
In fact, modularity itself is a black swan, constantly attracting you to feel its charm. It is beautiful, but while appreciating beauty, don’t forget to distinguish between fiction and reality.
Unreal is a modular tool created by someone else through their own experience that you enjoy using. Reality means you can’t use your own experience to create the same thing.
These tools do improve productivity twice as fast, but this is an illusion. Because, you are blinded by the great efficiency, when you leave the tool, you find that you are nothing, nothing. In other words, you can be replaced at any time, and you’re just a cog in the downstream of modularity, with no knowledge of the developers upstream.
You don’t know what the underlying logic of the module is, how it’s been upgraded iteratively, what it’s been through from scratch. That’s why people coming out of highly modular companies don’t seem to be as competent.
But it’s really hard to understand the logic of modular upper developers, and it doesn’t work for the average person, so there’s no other way to apply it. That’s true and that’s not true.
Limited by our own capabilities and resources, it is difficult to understand how this black box works. But do we do nothing?
3/ In fact, there are things we can do
** First of all, we can communicate with the developer, give him your feedback, invite him to improve, ** he will be willing to listen to your opinions. At the same time, you can also get the original intention of the developer to create this module and some underlying logic.
Like the great colleague at the beginning. By communicating with him, we can understand what the logic of the tool is. It doesn’t matter if you don’t know programming, you can learn it, you can give it to outsourcing, it’s not the point, the key is to grasp his thought, how to repeat things modular concrete thinking, this is what we need to deeply understand and think about.
Why didn’t we think of it, but he thought and acted on it? I think it’s a question we should think about.
** Secondly, through deep thinking, internalize this process thinking and graft it into your own work. In other words, build your own modular tools from someone else’s modular tools. Because it’s your own modular tool, it brings efficiency, it’s true, it can’t be copied.
Here, we use the core innovation thinking of “A Brief History of Innovation” : root innovation, domain innovation and dimension innovation. We need to cultivate top-down thinking to solve problems with innovative thinking.
Through the theory in the book, we can know that highly complex innovation can be regarded as a dimensional innovation, which is composed of N domain innovations of the same dimension. In the case of that colleague’s gadget, we can break it down into: JAVA language and 3D modeling software as two domain innovations; Then they are separated into the root innovation: circular judgment statement and sketching. The logical framework is to control the generation, copy and paste of sketching through circular judgment statement, and finally realize the automation function.
That said, it’s important to understand the underlying logic, not only to help us think deeply about creating our own modular platform, but also to avoid the awkward situation of running after someone else and not knowing why.
Next time you come across a gadget developed by someone else, please use it carefully, think about it carefully, and disassemble and analyze it.
While enjoying the productivity it brings, keep thinking, what else would I do without it? Is there another way? Can you try making a different tool yourself?
Build their own modular platform, let others to cheer! That’s what we really need to do.
Summary and reflection
If you want to learn Java engineering, high performance and distributed, micro services, Spring, MyBatis, Netty source analysis friends, you can join **Java backend technology group: 819940388, or pay attention to wechat public number: Java information library, reply to “architecture”, ** not only share free large-scale Internet Java technology video to everyone, but also teach you the right way of thinking to help you say goodbye to confusion, while there will be career planning, enterprise push, etc. Our aim is to set up a circle of sharing, learning, communication, career planning, mutual help and mutual progress.