I forked the source code of Ruby China a few days ago, and was completely confused by the unfamiliar Ruby technology stack.
It's obviously a week, and the code doesn't lie. So I changed the text and filed a pull request. Starting from the macro When I learn about a new technical term, I will not get stuck into the details directly, but grasp it from a macro perspective. Understand its background, why it appears, what problems it solves, what similar technologies there are, and how we worked before it. With a macro understanding, I can easily associate it with the technology I am familiar with, so as to understand it faster.
Practice makes perfect I opened the official website and found a great Try it out. I spent 10 minutes playing it to get a general understanding of how to play it, and then I solved the actual problem.
But I tragically discovered that the entire record was replaced. Well, this is a document-based database. So I searched on Google: How to update specific field in mongodb The answer was soon found.
My needs here are:
Problem solved. As I get more and more involved, I encounter more and more problems. I will put every problem I solve in my Evernote so that I can find the answer quickly next time I encounter it. When I found postach.io, a blog system that can be synchronized with Evernote, I opened such a blog, so that others can find the answer more easily when they encounter the same problem. When I am really interested in a technology and have enough time to learn it, I usually follow the steps below.
Teaching is the most important thing After enough practice, I may feel that I have mastered the technology. But when I try to express it, I will be surprised to find that there are still many concepts that I don't quite understand. So I will look up information and improve my system. Only when I express what I have learned in my own language and the audience can understand it, I have truly mastered the technology. Postponing learning A colleague who reads more than 100 books a year said:
Nowadays, new technologies emerge in an endless stream, and we don't have enough time to learn each one in depth. For most technologies, we only need to understand the concept part, understand it from a macro perspective, and decide whether we want to learn it in depth. With this understanding, you can easily chat with others, and you can also make some preparations for future technology selection. When facing real needs, or when you have enough time to make technical preparations, you can enter the practical part. |
<<: Several valid reasons for refusing to fix a bug
>>: Why app design hurts app development
Tuchong Creative Recently, a team from the Biorob...
1. Document Overview and Analysis Purpose Experie...
Some time ago, Bilibili released its Q3 financial...
Quickdraw’s CNN-RNN model The quickdraw model use...
1. Social advertising helps app growth Only throu...
The fourth quarter of 2019 has just passed. What ...
Course Catalog: The 81 practical lessons of Sheng...
In this era when traffic is becoming more and mor...
In 2017, after Pinduoduo launched a large number ...
Review of this article: Pa Lizhe, chief physician...
As a veteran office takeout delivery buyer, I oft...
More and more businesses are paying attention to ...
At present, Tianwen-1 is about 184 million kilome...
Not long ago, a friend of mine who works in the c...
From products like WeChat and Zhihu, I feel that ...