| ;; To run export from Bash: | |
| ;; emacs -batch -l ~/.emacs.d/init.el -eval "(org-agenda-export-to-ics)" -kill | |
| ;; if [[ "$?" != 0 ]]; then | |
| ;; notify-send -u critical "exporting org agenda failed" | |
| ;; fi | |
| (setq org-directory "~/Dropbox/org/") | |
| (defun set-org-agenda-files () | |
| "Set different org-files to be used in `org-agenda`." | |
| (setq org-agenda-files (list (concat org-directory "things.org") |
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.
EDIT: Well this has been linked now so just an FYI this is still TBD. Feel free to comment if you have suggestions for improvements. Also here is an unrolled Twitter thread of a lot of the tips I talk about on here.
I've been doing frontend for a while now and one thing that really gripes me is the interview. I think the breadth of knowledge of a "Frontend Engineer" has been so poorly defined that people really just expected you to know everything. Many companies have made this a hybrid role. The Web is massive and there are many MANY things to know. Some of these things are just facts that you learn and others are things you really have to understand.
Every time I interview, I go over the same stuff. I wanted to create a gist of the TL;DR things that would jog my memory and hopefully yours too.
Lots of these things are real things I've been asked that caught me off guard. It's nice to have something you ca
| [ | |
| { | |
| "id": "2baf70d1-42bb-4437-b551-e5fed5a87abe", | |
| "name": "Total Used", | |
| "total": "20.00", | |
| "mobile": "16.00", | |
| "network": "3.00", | |
| "roaming": "1.00", | |
| "mobile_data": [ | |
| "76" |
| [{ | |
| "contest_id": 1, | |
| "contest_name": "Treeflex", | |
| "start_date": "5/11/2019", | |
| "end_date": "8:27 AM", | |
| "end_time": "12:14 PM", | |
| "details": "Cum sociis natoque penatibus et magnis dis parturient montes, nascetur ridiculus mus. Vivamus vestibulum sagittis sapien. Cum sociis natoque penatibus et magnis dis parturient montes, nascetur ridiculus mus.\n\nEtiam vel augue. Vestibulum rutrum rutrum neque. Aenean auctor gravida sem." | |
| }, { | |
| "contest_id": 2, | |
| "contest_name": "Toughjoyfax", |
| body { | |
| background-image: linear-gradient(-225deg, #5d9fff 0%, #b8dcff 48%, #6bbbff 100%); | |
| height: 100%; | |
| margin: 0; | |
| background-repeat: no-repeat; | |
| background-attachment: fixed; | |
| } | |
| .example-enter { | |
| opacity: 0.01; |
I have moved this over to the Tech Interview Cheat Sheet Repo since a gist is too difficult to maintain as an open source endevaor and there is no way to version it. I have updated below, but I will not be able to keep this one up to date so please checkout the repo instead. The below is just for some preservation for those who stumble across here.
This list is meant to be both a quick guide and reference for further research into these topics. It's basically a summary of that comp sci course you never took or forgot about, so there's no way it can cover everything in depth.
Please see the Tech Interview Cheat Sheet Repo
I hereby claim:
- I am vetrivelcsamy on github.
- I am vetrivelcsamy (https://keybase.io/vetrivelcsamy) on keybase.
- I have a public key ASAdPRMm7KBIIUSo_6_7oM1K84iL7Z-SUZCnWIQ5-09jrQo
To claim this, I am signing this object: