- What do you like best about working there?
- What do you like least?
- How would you describe this company's culture? engineering culture?
- What causes the most conflict among employees here?
- What would you change if you could?
- How has the company changed in the past five years? How do you think it will change in the next five?
- How long has the longest serving team member been there?
- What's the average or median tenure?
# Bazarr downloads subtitles | |
version: "3.4" | |
services: | |
bazarr: | |
image: linuxserver/bazarr:1.0.5-development | |
container_name: bazarr | |
restart: unless-stopped | |
environment: | |
- TZ=Europe/London |
interface Value<T> { | |
kind: "value"; | |
value: T; | |
} | |
interface Error<T> { | |
kind: "error"; | |
error: T; | |
} | |
export type Result<T, E> = Value<T> | Error<E>; | |
export type Optional<T> = T | undefined; |
Hopefully this will answer "How do I setup or start a Django project using REST Framework and ReactJS?"
I created this because it was SUCH a pain in the ass setting up a project using all the latest technologies. After some research, I figured it out and have it working. The repo that implements this is located here. Feel free to use it as a boilerplate ;)
Main features:
- Django REST APIs
- ReactJS with Redux Pattern
- Webpack module bundler manager
By: @BTroncone
Also check out my lesson @ngrx/store in 10 minutes on egghead.io!
Update: Non-middleware examples have been updated to ngrx/store v2. More coming soon!
Table of Contents
We will compare ASP.NET and Node.js for backend programming.
Source codes from examples.
This document was published on 21.09.2015 for a freelance employer. Some changes since then (14.02.2016):
- Koa.js no longer uses co-routines, it has switched to Babel's
async/await
.yield
andawait
are used almost in the same way, so I see no point to rewrite the examples.
When unsing docker compose you can have a problem with the order of dependent linked containers
The solution is to start a script which tries to access a service and waits until it gets ready before loading your program
NOTE: This guide has moved to https://github.com/bpierre/switch-to-vim-for-good
This guide is coming from an email I used to send to newcomers to Vim. It is not intended to be a complete guide, it is about how I switched myself.
My decision to switch to Vim has been made a long time ago. Coming from TextMate 1, I wanted to learn an editor that is Open Source (so I don’t lose my time learning a tool that can be killed), cross platform (so I can use it everywhere), and powerful enough (so I won’t regret TextMate). For these reasons, Vim has always been the editor I wanted to learn, but it took me several years before I did it in a way that works for me. I tried to switch progressively, using the Janus Vim distribution for a few months, then got back to using TextMate 2 for a time, waiting for the next attempt… here is what finally worked for me.
Original gist with comments: https://gist.github.com/bpierre/0a0025d348b6001394e0
#time "on" | |
#load "Bootstrap.fsx" | |
open System | |
open Akka.Actor | |
open Akka.Configuration | |
open Akka.FSharp | |
open Akka.TestKit | |
// #Using Actor |
See https://github.com/romainl/idiomatic-vimrc for an up-to-date version.