Fortune quadrophobiac

## gist:f5e9f8a22de3f6dde48e
To clarify if non-blocking fashion means making the CSV parsing CPU bound rather than IO Bound, and to check what refactoring is desired (I had previously moved the parse_csv methods to a separate file, not sure if this is required or not, and if it is required it will require rewriting a lot of tests)

stephenfortune [2:13 PM]
I think that the existing code already has the CSV parsing as CPU bound but it would be helpful to clarify

James Smith [2:14 PM]
in my mind it’s more that no matter how the parsing is bound (CPU or IO), you can’t tell what it’s doing halfway through - and that’s what we need to be able to do.

James Smith [2:14 PM]
if that makes sense. And if it is in fact correct. Might not be

## index.html
<body>
  <div id="container" class="container">
      walla walla glub glub
  </div>
</body>


## gist:32fc608b5e8a8c23b0d8
git clone https://github.com/theodi/chef-csvlint.git
cd chef-csvlint/
rbenv local 2.1.6
gem install bundler -v 1.10.5
bundle exec kitchen converge

to sanity check your local env
which ruby # should return /Users/$USERNAME/.rbenv/shims/ruby
which gem # should return /Users/$USERNAME/.rbenv/shims/gem
ruby -v # returns ruby version

## discussing OO principles with ODI engineers
@pikesley: @pezholio  I'm aware this may not arise in the time remaining on the internship period, but if you do decide to write a gem for something-something-ODI could you alert us?

Sam [3:25 PM]
I can show you build-a-gem-101 in like an hour

Sam [3:25 PM]
Up to and including putting it through travis and publishing to rubygems

stephenfortune [3:25 PM]
I'd love to see the travis part, but I'm interested in being a fly on the wall to the rationale of creation which was discussed earlier
	To clarify if non-blocking fashion means making the CSV parsing CPU bound rather than IO Bound, and to check what refactoring is desired (I had previously moved the parse_csv methods to a separate file, not sure if this is required or not, and if it is required it will require rewriting a lot of tests)

	stephenfortune [2:13 PM]
	I think that the existing code already has the CSV parsing as CPU bound but it would be helpful to clarify

	James Smith [2:14 PM]
	in my mind it’s more that no matter how the parsing is bound (CPU or IO), you can’t tell what it’s doing halfway through - and that’s what we need to be able to do.

	James Smith [2:14 PM]
	if that makes sense. And if it is in fact correct. Might not be
	<body>
	<div id="container" class="container">
	walla walla glub glub
	</div>
	</body>
	git clone https://github.com/theodi/chef-csvlint.git
	cd chef-csvlint/
	rbenv local 2.1.6
	gem install bundler -v 1.10.5
	bundle exec kitchen converge

	to sanity check your local env
	which ruby # should return /Users/$USERNAME/.rbenv/shims/ruby
	which gem # should return /Users/$USERNAME/.rbenv/shims/gem
	ruby -v # returns ruby version
	@pikesley: @pezholio I'm aware this may not arise in the time remaining on the internship period, but if you do decide to write a gem for something-something-ODI could you alert us?

	Sam [3:25 PM]
	I can show you build-a-gem-101 in like an hour

	Sam [3:25 PM]
	Up to and including putting it through travis and publishing to rubygems

	stephenfortune [3:25 PM]
	I'd love to see the travis part, but I'm interested in being a fly on the wall to the rationale of creation which was discussed earlier