staltz

The introduction to Reactive Programming you've been missing

(by @andrestaltz)

---

This tutorial as a series of videos

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.

---

zakariaf

Rails 7 new features. Before and After

• Add ComparisonValidator
• PostgreSQL generated columns
• PostgreSQL custom enum types
• Add tracking of belongs_to association
• association_previously_changed? method
• Add invert_where method
• Add associated method
• Add missing method
• Active Record Encryption

cheynewallace

# Usage:  powershell ExportSchema.ps1 "SERVERNAME" "DATABASE" "C:\<YourOutputPath>"


# Start Script
Set-ExecutionPolicy RemoteSigned

# Set-ExecutionPolicy -ExecutionPolicy:Unrestricted -Scope:LocalMachine
function GenerateDBScript([string]$serverName, [string]$dbname, [string]$scriptpath)
{
  [System.Reflection.Assembly]::LoadWithPartialName("Microsoft.SqlServer.SMO") | Out-Null

kachayev

Channels Are Not Enough

... or Why Pipelining Is Not That Easy

Golang Concurrency Patterns for brave and smart.

By @kachayev

Intro

rushilgupta

INTRO

Concurrency is a domain I have wanted to explore for a long time because the locks and the race conditions have always intimidated me. I recall somebody suggesting concurrency patterns in golang because they said "you share the data and not the variables".

Amused by that, I searched for "concurrency in golang" and bumped into this awesome slide by Rob Pike: https://talks.golang.org/2012/waza.slide#1 which does a great job of explaining channels, concurrency patterns and a mini-architecture of load-balancer (also explains the above one-liner).

Let's dig in:

Goroutines

joshdover

Idiomatic React Testing Patterns

Testing React components seems simple at first. Then you need to test something that isn't a pure interaction and things seem to break down. These 4 patterns should help you write readable, flexible tests for the type of component you are testing.

Setup

I recommend doing all setup in the most functional way possible. If you can avoid it, don't set variables in a beforeEach. This will help ensure tests are isolated and make things a bit easier to reason about. I use a pattern that gives great defaults for each test example but allows every example to override props when needed:

sergey-tihon

#r @"packages\Streams.0.2.5\lib\Streams.Core.dll"

open System
open System.IO
open System.Collections.Generic
open Nessos.Streams

// make Visual Studio use the script directory
Directory.SetCurrentDirectory(__SOURCE_DIRECTORY__)

david90

#!/bin/bash -e
# Make sure you have installed ImageMagick
# http://cactuslab.com/imagemagick/

# Ensure we're running in location of script.
cd "`dirname $0`"

for f in *; do
  if [[ $f == *@3x* ]];
    then

dmarcato

def toCamelCase(String string) {
    String result = ""
    string.findAll("[^\\W]+") { String word ->
        result += word.capitalize()
    }
    return result
}

afterEvaluate { project ->
    Configuration runtimeConfiguration = project.configurations.getByName('compile')

Zoramite

# Verifies the connectivity and validity of the objects in the database
git fsck —unreachable

# Manage reflog information
git reflog expire —expire=0 —all

# Pack unpacked objects in a repository
git repack -a -d -l

# Prune all unreachable objects from the object database