Juanito JuanitoFatas

RedDotRubyConf 2016 links & resources

📆 Jun 23-24, 2016

🌏 Web site: http://reddotrubyconf.com/ Twitter: http://twitter.com/reddotrubyconf

💁 Ping me @cheeaun on Twitter or leave a comment below if you found some awesome stuff for #rdrc2016. This gist will be updated whenever there's new stuff.

🕙 Previously, on RedDotRubyConf...

Product managers

Seek out failure, it teaches us to think like a scientist. If you start with a hypothesis, then try to prove yourself wrong, you’re bound to make much better decisions. You have to be willing to fail, and that in itself is going to help you build confidence and be more convicted about what your strategy is in the end.
There are hundreds of methods for building products and running teams. As a quality PM, it's important to have an open mind about all of it, but finding your own process and philosophy can be grounding. It helps you find your pillars so that you don't smash into things while you're building. Remember, however, that you can always find a budget for remodeling. 😉
The beauty of a good process is when it just becomes how you do your work. When you forget you're following a process at all is when you know the process is working for you, your team, your company, and your customers.
The advice I give new Product Managers or PMs coming onto a team for the first

Finding a Ruby memory leak using a time analysis

When developing a program in Ruby, you may sometimes encounter a memory leak. For a while now, Ruby has a facility to gather information about what objects are laying around: ObjectSpace.

There are several approaches one can take to debug a leak. This discusses a time-based approach, where a full memory dump is generated every, say, 5 minutes, during a time that the memory leak is showing up. Afterwards, one can look at all the objects, and find out which ones are staying around, causing the

Project Title

One Paragraph of project description goes here

Getting Started

These instructions will get you a copy of the project up and running on your local machine for development and testing purposes. See deployment for notes on how to deploy the project on a live system.

	Links:

	A Visual Introduction to Machine Learning
	http://www.r2d3.us/visual-intro-to-machine-learning-part-1/

	UC Berkeley CS188 Intro to AI -- Course Materials
	http://ai.berkeley.edu/home.html

	Eyeo 2016 – Gene Kogan
	https://vimeo.com/180044029

	echo '{
	"scripts": {
	"watch": "nodemon -w src -w jasmine -e html,js,jsx --exec npm run build",
	"prebuild": "npm run test",
	"build": "webpack -d",
	"prestart": "npm run build",
	"start": "webpack-dev-server --inline --hot --content-base dist",
	"production": "NODE_ENV=production webpack -p",
	"test": "babel-node jasmine/run.js"
	}

	module Enumerable
	def first_to_finish
	threads = collect { \|args\| Thread.new { yield(args) } }
	loop until done = threads.detect { \|t\| !t.alive? }
	threads.each(&:kill)
	done.value
	end
	end

	puts [5, 3, 1, 2, 4].first_to_finish { \|x\| sleep x }

	#!/usr/bin/env ruby --disable-gems

	# Tab completion for minitest tests.
	#
	# INSTALLATION:
	#
	# 1. Put this file in a directory in your $PATH. Make sure it's executable
	# 2. Run this:
	#
	# $ complete -o bashdefault -f -C /path/to/this/file.rb ruby

	require 'fileutils'

	namespace :html2sprockets do

	desc "Setup env for gem creation"
	task :env do
	@gemname = ENV.fetch('NAME')
	@gemdir = File.join(ENV.fetch('GEMDIR', 'vendor/gems'), @gemname)
	@asset_dst_path = File.join(@gemdir, ENV.fetch('DST', 'vendor/assets'))
	@asset_src_paths = ENV.fetch('SRC').each_line.collect(&:strip)