Brian Cobb bcobb

todo

Storm Threequal js vs ruby

Keynote

The E myth Org chart for yourself

QFD = ideas into actionable items

Demanding software professionalism

Presented by Bob Martin in Tampa, Florida on 11 April 2012.

Miscellany

“Uranus is not a naked–eye object under any circumstances.”

Copernicus’ motivation was religious, not scientific! Galileo looked at the phases of Venus to determine its orbit in relation to Sol.

Bob: How do you become unafraid of your code?

Getting the most out if a Conference - Jeff Casimir

Why are we here? Ruby community is awesome New people are awesome Developers are exhausted by social interaction Recharge with a movie by yourself Conferences are about starting conversation Its hard Introvert != shy

About

This gist is a collection of my rough notes from Strange Loop 2012.

@jasonrudolph on Twitter | @jasonrudolph on GitHub

Did I Mention That They're Rough?

Notes On Strange Loop 2013

The second Strange Loop I've attended was truly an amazing conference like no other. Last year's was fantastic, but this year was just, well, you really had to be there. Even so, I'll try to give a summary of stuff that happened.

Negatives

To get it out of the way now, these are the things I didn't like:

Curry

Curry checks that committers in a GitHub Pull Request have signed Chef's CLA in Super Market.

Intro

The general goal of curry is to verify that committer(s) opening a pull request in a Chef Inc. repo have signed a CLA. If they have signed a CLA, Super Market will leave a comment letting Chef Inc. know that the user has signed a CLA. If they have not, Super Market will leave a comment letting Chef Inc. and the committer(s) know they have not signed a CLA, while instructing the committer(s) to sign a CLA. When the Pull Request is opened, a ticket is opened in the ticket tracking system being used (in Chef's case, JIRA).

Major parts of Curry include:

	# MOTIVATION: As rails apps are growing, people are noticing the drawbacks
	# of the ActiveRecord pattern. Several apps I have seen, and several
	# developers I have spoken to are looking towards other patterns for object
	# persistence. The major drawback with ActiveRecord is that the notion
	# of the domain object is conflated with what it means to store/retrieve
	# it in any given format (like sql, json, key/value, etc).
	#
	# This is an attempt to codify the Repository pattern in a way that would
	# feel comfortable to beginner and seasoned Ruby developers alike.
	#

	<input placeholder="ping something" /><button>ping!</button>
	<pre></pre>
	<script src="//localhost:8888/socket.io/socket.io.js"></script>
	<script>
	(function () {
	var socket = io.connect("//localhost:8888"),
	pre = document.querySelectorAll("pre")[0],
	input = document.querySelectorAll("input")[0],
	button = document.querySelectorAll("button")[0];

	require 'thread'

	class Actor
	class ActorDied < RuntimeError; end
	def self.queue
	@queue \|\|= Queue.new
	end

	def self.push(x)
	queue.push(x)