;; sort out backspace in .emacs on monch | |
(keyboard-translate ?\C-h ?\C-?) | |
(keyboard-translate ?\C-? ?\C-h) | |
(global-set-key "\C-h" 'delete-backward-char) |
(by @andrestaltz)
If you prefer to watch video tutorials with live-coding, then check out this series I recorded with the same contents as in this article: Egghead.io - Introduction to Reactive Programming.
We are building a Node.js service which will need asynchronous support for tasks like sending emails. Here's our evaluation:
- kue
- https://github.com/Automattic/kue
- Good: Seems well documented
- Good: Supports retries and backoff
- Good: Uses Redis so 1 less thing to maintain
- Bad: Only supports Redis so have to wary of key eviction at later stages of growth
- Bad: Slow to resolve issues
- http://isitmaintained.com/project/Automattic/kue
Основная задача тестового не узнать как сильно вы знаете React, а посмотреть насколько хорошо вы сможете разобраться с новыми технологиями в относительно короткий срок. В идеале, на него нужно потратить не более 3 дней. А так - делайте сколько делается, пока мы не закроем вакансию ;)
Нужно написать одностраничное приложения для просмотра фильмов с помощью The Movie Database API.
При открытии приложения, должен отображаться список популярных фильмов с пагинацией или динамической подгрузкой (на выбор). Также на странице должно быть поле для поиска. Когда ты вводишь туда какой-то текст, должны отобразиться фильмы которые ему соответствуют. Для каждого фильма в списке должен отображаться список жанров (названий жанров, не айдишек), к которым он принадлежит.
import { Action } from "redux"; | |
import { ActionsObservable, Epic, StateObservable } from "redux-observable"; | |
import { TestScheduler } from "rxjs/testing"; | |
const assertDeepEquals = (actual: any, expected: any) => { | |
expect(actual).toEqual(expected); | |
}; | |
export const marbleTest = <T extends Action, O extends T = T, S = void, D = any>({ | |
epic, |
This is my lightning talk submission to ReactiveConf 2018 https://reactiveconf.com/
In this talk, I want to share my experience gained during the development of frontend applications in several programming languages.
I think it's not a secret for anybody that developing large JavaScript applications is not so easy as it seems at first glance. We all want something simpler and more reliable. Therefore, many developers and even entire companies switch to different, compiled in JavaScript, programming languages. The bulk of such transitions is accounted for TypeScript and flow, and often, developers faced with more problems than they were before.
I wasn't the exception. Moving to a new project, I started using TypeScript and was disappointed. Luckily in my next project I used ClojureScript and it was like everything is illuminated!