Alyson shtakai

Slides

That is is basically a "fork" of blog article i'm constantly returning to. It seems that the blog is down:

Dave Bass proposed this which I picked up for my implementation (here for an 8-chars token):

Never use float for performing arithmetic calculations relating to money.

Floating numbers can sometimes show funky behaviour. It is not Ruby’s fault but the very implementation of floating numbers raises precision issues.

Examples of odd behaviour:

	function createStore(reducer) {
	const store = {
	state: {},
	reducer,
	dispatch(action) {
	this.state = this.reducer(action, this.state)
	}
	}

	store.dispatch({})

	source "https://rubygems.org"

	# Fixed order
	gem "rails"

	# Alphabetical order
	gem "activerecord-belongs_to_if"
	gem "bcrypt"
	gem "email_validator"
	gem "execjs"

	require 'openid_connect'

	OpenIDConnect.debug!

	config = {
	client_id: 'YOUR-CHANNEL-ID',
	client_secret: 'YOUR-CHANNEL-SECRET'
	}

	client = OpenIDConnect::Client.new(

	// Note: You must restart bin/webpack-watcher for changes to take effect

	var path = require('path')
	var webpack = require('webpack')
	var merge = require('webpack-merge')

	var config = require('./shared.js')

	var devconfig = {
	devtool: 'sourcemap',

	module ActiveJobRetryControlable
	extend ActiveSupport::Concern

	DEFAULT_RETRY_LIMIT = 5

	attr_reader :attempt_number

	module ClassMethods
	def retry_limit(retry_limit)
	@retry_limit = retry_limit