After hitting the Qiita API with Python to get a list of articles for beginners, we will visit the god articles

Introduction

Qiita's "Beginner" tag and "New programmer support" tag articles for beginners As a new QA engineer, all of them are very helpful to me. Unfortunately, the individual tag page only lists trends and new articles, The specifications make it difficult to find good articles from the past. In this article, we will first use the Qiita API to write articles for beginners (articles tagged as: = "Beginner" OR "Support for new programmers"). After creating a program that outputs everything, the result of reading each article in the output list in descending order of likes I will introduce the god articles that I felt "This is ridiculously helpful!"

• • Note: This time, we filter by the number of likes, but the articles that are useful to you are god articles regardless of the number of likes !! *

Thing you want to do

1. Get all articles for beginners and output to CSV
2. Read the CSV with spreadsheet software and sort the list in descending order of "most likes"
3. Worship in order from the top

Make a program

Consider how to "take all articles for beginners and output to CSV"

I simply thought about it like this.

1. Get all articles with "Beginner" tag OR "New programmer support" tag with API
2. Extract only the data you need
3. Export the data to CSV

Read the API specifications and consider how to get the data and the required data

If you read Official documentation of Qiita API, you can see the following.

• You can get articles by throwing a search query with the number of pages and tags in "GET / api / v2 / items".
• The total number of elements (number of articles) is included in the Total-Count response header

• You can get all articles by first throwing a search query to get the number of articles and then converting it to the number of pages

• For this purpose, the following data of each acquired article is sufficient

• title
• url
• tags --As supplementary information, there are cases where the content cannot be understood at a glance with just the title.
• updated_at --Because it is necessary to confirm that the specifications have not changed if the technical information is too old
• likes_count --For screening due to the huge number of articles

Implement a little

** I have put the code implemented based on the above examination, its explanation, and sample output file on GitHub. **

For implementation, I referred to the following article. Thank you! Get a list of articles I posted on Qiita

To worship

You can operate the list with Python, but it is troublesome, so this time I will read the CSV with spreadsheet software and edit it. Add a header column appropriately and sort in descending order in order of likes, and you're done. After that, I will go around the URL from the top. In my case, the articles I read and liked were "liked" + colored on the table.

As of November 20, 2019, the total number of articles acquired was 8642! I couldn't read the whole thing, so This time, I read 75 articles that had more than 1000 likes as of November 20, 2019.

Carefully selected !! Super God article list

The list below has read 75 god articles and 22 super god articles that impressed me especially! (Although there are a few, we have carefully selected such things as removing duplicated content) It is roughly categorized by content.

How to recommend work

• TIPS that inexperienced people may not recognize ――A collection of advice that includes not only work but also life. I feel that living ability is more important than technical ability.
• 7 Habits to Accelerate Programming Study ――It's called "programming study", but I think it can be applied to any kind of study.
• How much should I study for a new graduate? Was asked --Career theory. You will realize the importance of "determining your position".
• [For new SIer] Know-how collection not taught in training ――I was quite convinced that the place where I work is closer to SIer than the Web system.
• 25 mistakes that novice programmers tend to make ――It's for developers, but it's also very helpful from a QA perspective. Even if you're not a beginner, you often commit ...
• Personal summary when working as a new graduate trainer ――The theory that if a newcomer knows the trainer's point of view and the evaluator's point of view, he / she can understand the action to be taken.

How to write a document

• A certain anti-pattern when creating a document ――I'm sorry I didn't write in Japanese properly.
• 8 problems in Japanese that I would like you to fix before review --I'm sorry I didn't write in Japanese properly (Reprise)
• What I keep in mind when writing design documents for over 20 years as an engineer --Specific tips for writing documentation. Just being aware of this will make it much easier to read.

programming

• What I keep in mind when learning a new language --Specific "How to learn a programming language". Check this article first instead of buying a book all at once.
• Graduation exams from programming beginners should develop "Blackjack" ――It looks interesting, so I'll make it in Python next time.
• Only one principle I found after reading the readable code for the first time in 3 years ――If you want to write good code, be sure to read it.
• Why can't we read the official docs? ――There is something that is officially written about what you googled. If you are in trouble, first check the formula.

Computer Science * ~ Eventually here ~ *

• What is an algorithm! ?? ～ 6 carefully selected questions that can be enjoyed regardless of humanities and sciences ～ ――Purely interesting + super important algorithms are dealt with on the subject of competition professional problems.
• Master the sort! ~ Why learn sorting ~ --Speaking of algorithms, sorting. It reminds me of my school days (bloody tears)
• [For beginners] How to calculate the amount of calculation of the program ――It's a story about an order that comes up when you're studying algorithms.

Book / Article Summary

• Super summary of books and articles I want to dedicate to myself in my first year as a web engineer --Comprehensive introduction of useful knowledge for web engineers from a wide variety of genres. I was quite desperate to see if I could hold it so widely with three years of experience.
• Summary of articles I would like to recommend to new engineers because I personally became transcendent --Summary of recommended articles. All must read.
• [Translation] Technology Improvement Guide --Mainly introducing overseas programming / computer science services. Let's study English at this opportunity!

Information gathering / dissemination

• Summary of information gathering method for engineers ――For the time being, I registered all RSS and followed.
• All engineers should make it a habit to write technical articles ――The words "The person who wrote the article wins" are impressive. I started to write articles even if I couldn't help it.
• How to read English articles that took 3 years ――When you can read English articles, the amount of information you can access will increase explosively.

Impressions after reading

I read the so-called "buzzed" articles in order from the top,

• "Let's respect the people we work with" ** "Let's write in Japanese" * In fact, I feel that everything I say is similar, such as * "Let's learn computer science properly" *. ** The essence is surprisingly simple ~ **.

At the same time, I'm not satisfied just by reading the article, but I think I should actually take action. It's going to be a long way, but I can't help hurrying, so I'll keep going ...!