Nowadays, everyone decides to become a software developer, but the important thing is to be able to continue. Because many people back down from this decision. Of course, when this happens, all this enthusiasm and desire suddenly fades. But let's say you are not one of them and even you have reached a certain position in software. Come on, come here. I am waiting for you to get your coffee/tea. Let's see you in the next paragraph.
We cannot do many things we use in daily life by heart or we need to have a learning process on a subject we do not know. At this point, we need to reach the desired result early by doing the right research. When this early result is achieved, we reach the information in a short time. But on the other hand, we are moving away from the information we gain while doing research. Let's leave all these aside and assume that you have a problem and you need to solve it as soon as possible.
Researching on Google.
If it is a ready package, take a look at the documentation page.
Browse through the relevant repos and issues on Github.
Leave everything and move away from the problem.
Now that I've briefly mentioned what I'm going to talk about, shall we start with the first item?
Using Google effectively.
First of all, it is useful to stay away from Turkish searches. Okay, I agree. If you are doing research on a very general and widespread topic, you can use it. But otherwise, searching in English will make your job easier. While I am on the subject, I would like to give an example of a Turkish search.
"create javascript function"
You will reach a solution faster with these searches. Use it, thanks. But if your English is bad, you can go straight to English. You will feel more comfortable in the future.
From now on, I will talk about English searches. First of all, if you do not know how to do a part you need to do. A search like this will save your job. Let's learn how to complete in input.
In this way, we can reach dozens of sites on how to do it. You must have heard of Stackoverflow. If you say, "No, I don't go to any other site except Stackoverflow, I want to research there," you're welcome.
You have looked at so many sites but they are all related to jQuery. But you definitely want to do it with javascript. So let's filter the sites that have the word javascript. In this way, you will definitely see a word that has Javascript in bold in the results that appear on the search screen.
You are getting an error due to a recent version. If you want to look at recently shared content to solve this error. So let's easily filter by date. After typing what you need to search for in Google, you can follow the steps Tools > Anytime > "Select Date".
Browsing the documentation page.
As I mentioned above, you can easily find the documentation site by typing inurl:. You can also go directly to the documentation page and access it from the menus or the search section. I don't have many specific examples to suggest here. It's very simple, short and clear.
Getting lost in repos and issues on Github.
Here I'll talk about a method I've been thinking about lately. But no, not right away, keep reading, sir.
Let's say you are using a package. Let's say this is the Moment package. But you don't know how to use this package. First of all, you need to read the Readme file carefully. There is usually a section there about how to use it.
You saw a section about its use there and tried it. But there is a problem and it doesn't work. Now don't close the page right away, just wait. The first step is to go to the issues and research what has been written.
You did something to format the date with Moment, but it didn't work. So you can search and filter the issue page. You can find your answer from the answers given by filtering the questions people have asked. Sometimes the solution is reached faster this way, while sometimes it feels like you are going down a bottomless pit.
I would like to give you a tip here. You can usually find simple problems more easily in closed issues.
Yes, we can come to the method I mentioned at the beginning. Oh oh! I have been doing research on writing tests lately. As a result of the research, everything is actually explained in the tests, whether it is a function or the usage of the package. After all, there is an expected value for the test. In this way, the solution is reached quickly. Let's explain with an example.
I want to add 8 more minutes to a date I have. But I have no idea how to do this. I did so much research but I couldn't reach a result. Okay, calm down, open the repo, find the test files, open the relevant test and read the code. Oh, here we go. I can almost hear you say, "Wow, is it that easy?" Yes, it is :)
I didn't feel the need to explain the code, but I wanted to make a note. The first parameter is the operation performed, the second parameter is the expected result, and the third parameter is the description of the operation performed.
Couldn't you reach the conclusion? Time for a break!
Being exposed to a problem for a long time can make you blind after a while. Actually, taking a break will be very good for you. In this way, you will dig into the depths of the problem in a refreshed manner and say that the solution should be like this and you will reach the solution.
And don't tire yourself too much. Put on a nice song, sit back and drift away. What's that? Look, you found the solution. Well, sometimes it comes to you when you least expect it!
I wanted to scribble something before going to sleep. The idea of writing this article came from a tweet like this while I was browsing Twitter. I wanted to share what I know with the blog.
I was going to add that tweet to the article but I couldn't find it. That's why I can't add it.
