joakimk

Building a little list so I can more easily recommend the best talks and be able re-watch them myself.

Elm

• "Beyond Hello World and Todo Lists" by Ossi Hanhinen
  • Ossi shares practical experience of building several Elm apps.
• "The Clockwork Gardener: Growing an Elm App With Templates" by Jessica Kerr
  • Keeping maintainability of Elm while being able to do big sweeping changes like in a dynamic language.
• Q&A Panel (elm-conf 2016)
• Good and enteraining Q&A with many experienced Elm devs and Elm's creator.

joakimk

import UpdateList exposing (addOrUpdateById)

update msg model =
  case msg of
    NewOrUpdatedItem item ->
      ({model | items = model.items |> addOrUpdateById item}, Cmd.none)

joakimk

import {Socket} from "phoenix"

let socket = new Socket("/socket", { params: {} })
socket.connect()

let channel = socket.channel("updates", {})
channel.join()

// Reload the app if it's out of date when it joins the websocket
let revision = null

joakimk

# Based on https://gist.github.com/1718985

# Usage:
# 1) Put in spec/support/rspec_retries.rb
# 2) Call from spec_helper.rb: "RSpec::Retries.setup(config)"
# 3) Change around filter to suit your needs.

# Example output:
# ..............
#

joakimk

# config = ..
datacenter = VmwareDataCenter.new(config)

datacenter.create_vm(:name => "ServerName", :cpus => 1, :memory => 512, :disk => 5000,
                          :datastore => "VolumeName", :install_identifier_mac => "some mac addr",
                          :install_pxe_network_name => "network to look for pxe server on") 

# server cookbook https://github.com/joakimk/cookbooks/tree/master/pxe_install_server

joakimk

Using ActiveSupport::Dependencies outside of rails seems just as fast as doing manual requires. I've found this out by replacing hundreds of requires in a unit tested code base with ActiveSupport::Dependencies without any change to the time it takes to run the test suite.

Using ActiveSupport::Dependencies also allows you to have circular depedencies like class Foo::Bar in foo/bar.rb and class Foo in foo.rb that points to Foo::Bar in it's class definition (like in a rails validation).

The classical way of solving this without ActiveSupport::Dependencies is to do:

# foo/bar.rb
class Foo
 class Bar

joakimk

# Functional core
# Tested with unit tests. Mostly simple state based tests (like: invoice.gross_amount.should == 200).
class BuildInvoice
  def build
    # build invoice in memory..
  end
end

# Imperative shell
# Usually just tested with a single test to ensure it stores data in the database

joakimk

Association loading

# Load data from the DB
user = user_mapper.find(params[:id], include: { profile: :group })

# Use data in memory (you can't do lazy-loads with minimapper, which is probably
# a very good thing. Lets you avoid N+1 by default).
user.profile.group.name

joakimk

Writing this down in case it's useful for someone.

The reason why my oculus had inverted positional tracking (when I lean in, it moved me backwards in the 3d scene) was that my camera cable was broken. Ensure the little blue light is on when using the rift.

joakimk

class Address
  include Minimapper::Entity

  attribute :street
  attribute :postalcode
  attribute :city
  attribute :country

  validates :street, presence: true
end