Stuart Zahn szahn

Getting Started with Containers - Your Way

Here you can find a list of some quick tutorials and sample code to get you going quickly with containers on Azure.

On Your Computer

To quickly get started creating containers on your computer, download either Docker for Windows or Docker for Mac. One of the cool features of Docker for Windows is the ability to switch between Linux and Windows containers.

To get started creating containers with Docker, I recommend their Getting Started with Docker guide.

Code is clean if it can be understood easily – by everyone on the team. Clean code can be read and enhanced by a developer other than its original author. With understandability comes readability, changeability, extensibility and maintainability.

General rules

Follow standard conventions.
Keep it simple stupid. Simpler is always better. Reduce complexity as much as possible.
Boy scout rule. Leave the campground cleaner than you found it.
Always find root cause. Always look for the root cause of a problem.

Design rules

From my Pluralsight course: https://app.pluralsight.com/library/courses/asynchronous-javascript-reasoning/table-of-contents

Weather http://plnkr.co/edit/ZOAaSdtnfvR6WwiuVZ6s
Avoid Blocking – Red Background http://plnkr.co/edit/z29VyH5BPvC4oc40EyOu
setTimeout Pyramid Challenge http://plnkr.co/edit/DGiHFQOQfnipCcpex2RH
Drag and Drop Red Box http://plnkr.co/edit/SmSpPS5ZgPvkgn8RE6y1
Timer onReady http://plnkr.co/edit/gafgKCrxnDIJ6YaG9Jpx
Timer measure http://plnkr.co/edit/kPOgzEuIvUmN4o6Jenem
Progress Number Crunching - Web Worker https://plnkr.co/edit/Yy7BOZU9sIa8EyrxJwGH
Event Listeners Are Synchronous http://plnkr.co/edit/mDvSHpF3HcTjtvltGmQn

Interface Versioning (InterVer)

Never break backcompat, keep the API nimble

An extension of SemVer with a stricter (yet more realistic) backcompat guarantee, that provides more flexibility to change the API, for libraries that are packaged and downloaded (not services accessed remotely over the Internet (see Note 4)).

(That's my attempt to understand what problem Impulse solves and how. I am not a designer/developer of this scheme.)

Problem

Regular Bitcoin transactions are not guaranteed until mined sufficiently deep in the blockchain. Unconfirmed transactions can be observed nearly instantly, but they cannot be trusted (could drop out because of insufficient fees, or double-spent).

Impulse Overview

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.

	#!/bin/bash

	# Colors
	RED="\033[0;31m"
	ORANGE="\033[0;33m"
	GREEN="\033[0;32m"
	NC="\033[0m"

	# Messages
	OK="[OK]"

	# escape=`

	# Image with NET CORE installation to extract executables for final image
	FROM microsoft/aspnetcore:2.0.0-nanoserver As CoreBuild

	# Middleware image used to extract ASP.NET core module
	From microsoft/iis as WindowsBuild
	SHELL ["powershell", "-Command", "$ErrorActionPreference = 'Stop'; $ProgressPreference = 'Continue'; $verbosePreference='Continue';"]
	# Installing NET CORE webhosting in middleware image so latest module and configuration schema is extracted for final image
	ADD https://download.microsoft.com/download/B/1/D/B1D7D5BF-3920-47AA-94BD-7A6E48822F18/DotNetCore.2.0.0-WindowsHosting.exe ".\hosting.exe"

	import React from "react";
	import { render } from "react-dom";

	const ParentComponent = React.createClass({
	getDefaultProps: function() {
	console.log("ParentComponent - getDefaultProps");
	},
	getInitialState: function() {
	console.log("ParentComponent - getInitialState");
	return { text: "" };

	using Newtonsoft.Json;
	using System;
	using System.Collections.Generic;
	using System.Configuration;
	using System.IdentityModel.Tokens;
	using System.Linq;
	using System.Net.Http;
	using System.Security.Cryptography.X509Certificates;
	using System.Text;