| # study stream aliases | |
| # Requires https://github.com/caarlos0/timer to be installed. spd-say should ship with your distro | |
| declare -A pomo_options | |
| pomo_options["work"]="45" | |
| pomo_options["break"]="10" | |
| pomodoro () { | |
| if [ -n "$1" -a -n "${pomo_options["$1"]}" ]; then | |
| val=$1 |
| Авторизация\Регистрация | |
| https://github.com/jazzband/django-oauth-toolkit | |
| https://github.com/pennersr/django-allauth | |
| https://github.com/sunscrapers/djoser | |
| https://github.com/django-guardian/django-guardian | |
| https://github.com/flavors/django-graphql-jwt | |
| Защита входа | |
| https://github.com/jazzband/django-axes | |
| https://github.com/jazzband/django-defender |
Rust — невероятно быстрый язык для системного программирования без segfault'ов и с гарантиями потокобезопасности.
ИТТ мы можем объяснить базовые и продвинутые концепции языка, и программирования в целом, поможем вкатывающимся, подскажем что выбрать для веба, игр или, прости Абу, блокчейна.
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
All libraries have subtle rules that you have to follow for them to work well. Often these are implied and undocumented rules that you have to learn as you go. This is an attempt to document the rules of React renders. Ideally a type system could enforce it.
A number of methods in React are assumed to be "pure".
On classes that's the constructor, getDerivedStateFromProps, shouldComponentUpdate and render.
A collection of links to the excellent "Composing Software" series of medium stories by Eric Elliott.
Edit: I see that each post in the series now has index, previous and next links. However, they don't follow a linear flow through all the articles with some pointing back to previous posts effectively locking you in a loop.
| // slider | |
| $slick_slider = $('.slider'); | |
| settings_slider = { | |
| dots: false, | |
| arrows: false | |
| // more settings | |
| } | |
| slick_on_mobile( $slick_slider, settings_slider); | |
| // slick on mobile |
| /** | |
| * Dropzone Default Language Translate pack | |
| * | |
| * @lang Russian | |
| * @lang-ISO ru-RU | |
| * | |
| * @author ValeriaVG | |
| * @license Public Domain | |
| * @see https://gist.github.com/ValeriaVG/5ffcf92c98216e44e92d3db6a36ff838 |
