overview
Last year, I had a systematic understanding of the language, popularity, and scope on git, instead of just looking at the "2000 language ranking analysis" on other channels. In addition, last year, I actually mentioned that software-related expectations have declined. I expected this year to improve, but I didn’t expect that this year will directly come to "what has been hanged". The harsh winter and the extremely anxious market, many To some extent, it affects enthusiasm, and the staged experience can be summed up, "It is very difficult to think that you can change the world, but it is also very difficult to try to change the country. In the end, you find that the only person who can radiate and affect you is yourself ." This is more or less a bit , It means that the youthful spirit is not old and the heart is old. I hope that through effective analysis, I can gradually improve my cognition and look forward to making new changes.
gossip
My own essence has almost reconciled from last year to this year's way of thinking and my persistent attitude towards a single language skill. The general idea is that most of the work we do is actually responsible for the results. In this process, language , frameworks, and tools are all means to solve problems, and the final solution to the problem is the most important thing. Under this premise, it is necessary to properly consider subsequent changes and expansion risks, distinguish the workload, and determine the upper limit of technical realization. Overall, there is a forward-looking Basically, most of the work content can be effectively completed, and the energy saved can spread many interesting things.
Many people's attitude towards work seems to be serious and responsible, but in essence it is an attitude of coping and being responsible for the process. As for the quality of the results, they actually don't care at all, and even think that the impact of bad results has nothing to do with themselves No, after all, I don’t take the main responsibility, and joint and several liability is not considered a responsibility. This is a common and normal way of thinking. If things go on like this, habits will become natural, and I have set boundaries for myself. As long as the boundaries of the job are defined, such as front-end and back-end issues, management is usually loose. In this case, no one cares about the result. Anyway, there are difficulties in the process, opinions are raised, disputes continue, and differences often change from original technical differences to extremely irrelevant things. The benchmark side basically needs to be pulled back to maintain Disagreements are controllable in terms of the results of current events. There are often projects or products to control some differences in business and technical differences, especially in the front-end and back-end local technical gaps. Chicken and duck talk, dragging for a long time, limiting your own technical scope, is like hitting an egg against a rock with your own weakness and other people's strengths, and the result can only be a loss for both sides.
Therefore, what I want to say is, don’t reject doing more and learning more, as long as you have the opportunity to be more modest, it’s not good to make progress together. I won’t leave you alone, the more you do, the more painful you will be, and the greater the opportunities and strengths you will have for growth. There is no need to always deal with things with the idea of “there will always be troublesome people who want to hurt me”. I discussed with my colleagues before, he I always feel that my thought is: "Since we are all going to be ravaged, why not try to enjoy it", the words are ugly, but the meaning is well expressed. I think that when your role and ability do not occupy an effective proportion, all language They are very pale, why do you say it? In the world of adults, the heart is in chaos, the mouth is silent, the emotions are not visible, the standard of maturity and stability, this is the summary of many seniors, and I am gradually agreeing , Arming yourself is the process of increasing your own means of production. There is nothing to be ashamed of in terms of thinking.
My own situation is not very good in my imagination. Appropriate anxiety is the driving force, and our actual actions are a way to properly share anxiety. Therefore, in front-end, back-end, database, operation and maintenance, project lifecycle management, After having a certain grasp of product design, etc., it is necessary to have a proper understanding of the overall technical activity and direction, and the above is the reason for the driving force.
text
Let me talk about the source of data first. On GitHub, the largest gay dating site, open source developers from all over the world are working on millions of projects. There is a large amount of event information such as code documentation, repairs, and submission of BUGs generated every day. The GitHub Archive project collects the public data recorded on these GitHub timelines and archives them to make them easily accessible for further analysis. Use DBeaver to connect via HTTPS or JDBC
https://demo:[email protected]:8443
jdbc:clickhouse://github.demo.trial.altinity.cloud:8443
Direct connection via Web UI:
https://gh-api.clickhouse.tech/play?user=play
weekly language activity
Week content direction and language
It can be seen that the main direction of concentration is ChatGPT, or Python accounts for the majority.
java week content
Mainly focus on ChatGPT and middleware, interview
go language week content
Mainly focus on ChatGPT and blockchain
Contents of Vue Language Week
JavaScript language week content (React covered)
at last
The content of the first edition is relatively rough, mainly because the analysis method has just been fixed, and later it will gradually use Grafana for graphical processing, and try to present a clear Kanban. If there is any analysis method that you want to add, you can mention it, and I will try to add it next week , showing a relatively good analysis effect.