Inspired by dannyfritz/commit-message-emoji
See also gitmoji.
Commit type | Emoji |
---|---|
Initial commit | 🎉 :tada: |
Version tag | 🔖 :bookmark: |
New feature | ✨ :sparkles: |
Bugfix | 🐛 :bug: |
Inspired by dannyfritz/commit-message-emoji
See also gitmoji.
Commit type | Emoji |
---|---|
Initial commit | 🎉 :tada: |
Version tag | 🔖 :bookmark: |
New feature | ✨ :sparkles: |
Bugfix | 🐛 :bug: |
Windows Registry Editor Version 5.00 | |
[HKEY_CLASSES_ROOT\.md] | |
@="markdown" | |
[HKEY_CLASSES_ROOT\.md\ShellNew] | |
"NullFile"="" | |
[HKEY_CLASSES_ROOT\markdown] | |
@="Blank Markdown file" |
import { rateLimiting } from '../../fauna-queries/helpers/errors' | |
import faunadb from 'faunadb' | |
/* | |
* Ideally we limit the amount of calls that come to Login. | |
*/ | |
const q = faunadb.query | |
const { | |
If, | |
Epoch, | |
Match, |
I liked the way Grokking the coding interview organized problems into learnable patterns. However, the course is expensive and the majority of the time the problems are copy-pasted from leetcode. As the explanations on leetcode are usually just as good, the course really boils down to being a glorified curated list of leetcode problems.
So below I made a list of leetcode problems that are as close to grokking problems as possible.