pwstrick/daily: A Curated Chinese Frontend Interview Question Bank

What pwstrick/daily Actually Contains

This repository is a reading collection, not a program. The README describes it as a list of frontend interview questions gathered from various sources, sorted and edited by the author, with the stated goal of broad coverage and high readability. The topics listed include HTML5, ES6, React and Webpack, plus networking and soft skills.

The repository is organized into five top-level entries: README.md, article/, assets/, book/, and interview/. The interview/ directory holds the question files, and the README links each one with a count. HTML has 79 questions, CSS 100, JavaScript 149, ES6+ 89, React 102, networking 63, tools (webpack, Git and others) 60, algorithms 94, security 11, performance 16, soft skills 107, frontend general 33, Node.js 26, TypeScript 15, and Vue 42. There is also a link to a 30 seconds of code page described as short code snippets suitable for whiteboard interviews.

The audience is Chinese-speaking frontend candidates. Every question file is written in Chinese, and the README notes that questions can be discussed in the corresponding issue. The repository also links to the author's own related projects, including a frontend monitoring script called shin-monitor and a Zhihu column.

It is worth being clear about what this is not. There is no package, no CLI, no test runner, and no scoring. You read the Markdown files. The README gives no install instructions because there is nothing to install, and no releases are listed for the repository.

How the Question Files Are Organized

The structure is a flat set of Markdown files under interview/, one per topic, linked from the README with a question count. This is a deliberate choice: a candidate who wants to drill JavaScript opens interview/javascript.md, and someone revising CSS opens interview/css.md. Topic boundaries follow the usual frontend split rather than a difficulty gradient, so there is no beginner-to-advanced ordering implied by the file names.

The README does not document how individual questions are formatted inside each file, whether answers are included, or how the files are versioned between updates. That is a real gap. If you are evaluating the repository for a study plan, the only way to judge answer depth is to open the files themselves. The counts tell you volume, not quality.

The article/ directory is a separate track. It is organized by year, with files from 2019 through 2026, plus topic files for frontend optimization, design patterns, browser internals, Node.js, tooling and ChatGPT learning. The book/ directory holds a book list, a computer book ranking link, and two translated English interview books: 101 Toughest Interview Questions and The Interview Book: How to prepare and perform at your best in any interview.

The repository is not archived, and the last push was on 2026-09-08. That is recent, but the README itself says only that updates will continue, so the cadence is asserted rather than documented.

Reading pwstrick/daily Without Cloning It

There is no build step and no dependency to install. The README points readers at the GitHub-hosted Markdown files directly, and the simplest way to start is to open one of those files in a browser. If you do want the files locally, the repository's default branch is master, and the README links every question file by its full path on that branch.

To keep a local copy, clone the repository and change into it. The directory should then contain the same top-level entries listed in the README: README.md, article/, assets/, book/ and interview/.

git clone https://github.com/pwstrick/daily.git
cd daily

After that, open the question file for the topic you want. For example, the JavaScript set is at interview/javascript.md, which the README lists as 149 questions. The file is plain Markdown, so any text editor or Markdown viewer will render it.

If you prefer not to clone, the README links each file by full URL on the master branch, so opening that URL in a browser shows the rendered questions without any local setup.

The repository also links to a paid reading platform for the author's 算法躬行记 and 前端躬行记 series, and to a Zhihu column. Those are external destinations, not part of the repository, and the README gives no preview of their contents.

Where the Collection Falls Short

The main limitation is verification. The README says the questions were gathered from various sources and edited by the author, but it does not describe a review process, a correctness check, or a date attached to individual answers. Frontend answers age quickly, particularly around tooling and framework internals, and a question file that mixes questions from several years can contain answers that no longer match current behaviour. Nothing in the README tells you which entries were reviewed recently.

The second limitation is that this is a question bank, not a practice environment. There is no way to run the questions, no test harness, and no feedback loop. For algorithm practice specifically, the README links out to a LeetCode page and a paid series rather than embedding a judge. If your goal is to write and run code, this repository is the wrong tool.

The third is language. All question content is in Chinese. The two translated books are English-origin material rendered in Chinese. If you cannot read Chinese, the repository has little to offer beyond its link lists and the 30 seconds of code page.

Finally, the README does not document rollback, versioning of individual files, or a changelog. If you clone it and the author later restructures a file, you have no documented way to see what changed beyond the commit history.

How It Compares to a Structured Question Site

The closest alternative in kind is a maintained question-and-answer site such as the frontend section of a platform like LeetCode, or a curated English question list. The difference is in approach rather than topic coverage.

A site like LeetCode pairs each algorithm question with a runnable judge, test cases and a submission history. pwstrick/daily pairs questions with prose answers in Markdown, and for algorithms it links out to a separate LeetCode page and a paid series instead of providing a judge. That means the repository is better for reading and recall, and worse for measured practice.

Against a general English question list, the difference is language and framing. pwstrick/daily is written for a Chinese interview context, includes a soft skills file with 107 questions, and links to Chinese platforms and a WeChat group for discussion. An English list would not carry that context, and the soft skills section in particular is likely to reflect local interview norms.

The repository also differs from a single-author blog in that it aggregates links to other projects, including a page of recommended GitHub interview projects, a computer book ranking, and an English learning resource for Chinese speakers. That makes it partly an index and partly a question bank. The index value depends on the links staying current, and the README gives no link-checking process.

Maintenance, Licence and Upgrade Cost

The repository is not archived, and its last push was on 2026-09-08. That is within the recent window, so the project is not dormant. The README states that updates will continue and that questions will be supplemented, with discussion in the corresponding issue. It does not state a release cadence, and no releases are listed.

Upgrade cost is low in the mechanical sense. There is no dependency graph, no lockfile and no build. Pulling the latest changes is a git pull on the master branch, and the only thing that can break is a link or a file path you have bookmarked. If you have forked the repository and added your own notes, a rebase against master is the only maintenance work the structure implies.

The licence is not stated in the repository metadata, and the README does not include a licence section. That matters if you plan to republish, translate or bundle the questions into your own material. Without a declared licence, the default position is that the author retains rights, and you should treat redistribution as something to clarify with the author rather than assume is permitted. This is not legal advice; check the repository for a licence file and contact the author through the WeChat ID given in the README if you need permission.

The README also includes a donation image and a page-view badge. Neither affects use of the content.

Editorial conclusion

pwstrick/daily suits Chinese-speaking frontend engineers preparing for interviews, or anyone who wants a classified question index to study from. It does not suit readers who need English-language material, runnable practice environments, or automated grading. Before relying on it, open the interview/html.md and interview/javascript.md files and check whether the question depth and answer style match what you need, since the README gives counts but not answer quality.

Frequently asked questions

Official sources

1. Issues
2. pwstrick/daily on GitHub
3. README