kerrizor

’Twas brillig, and the slithy git repos
Did gyre and gimble in the wecks:
All mimsy were the borogoves,
And the mome raths Mutex.

“Beware the legacy code, my son!
The classes that bite, the patches that catch!
Beware the Gemfile.lock, and shun
The frumious monkey patch!”

kerrizor

’Twas brillig, and the slithy git repos
Did gyre and gimble in the wecks:
All mimsy were the borogoves,
And the mome raths Mutex.

“Beware the legacy code, my son!
The classes that bite, the patches that catch!
Beware the Gemfile.lock, and shun
The frumious monkey patch!”

kerrizor

In test/test_helper.rb...

### Bullet (N+1 queries)

if ENV['BULLET']
  Bullet.enable = true

  require 'minitest/unit'

kerrizor

[alias]
    review = log -p --reverse -M -C -C --patience
    review-topic = !sh -c 'git review ${1}^1..${1}^2' -
    view-topic = !sh -c 'git log --reverse --stat -M -C -C ${1}^1..${1}^2' -

kerrizor

Many of the best resources on the actual data behind code metrics are in white papers, dry IBM and .NET "Developer Zone" journals, and in Java land. Here's a bunch of links from when I was putting together my code metrics talk I gave at Steel City a couple years ago.

"Perfection is achieved, not when there is nothing more to add, but when there is nothing left to take away." -- Antoine de Saint-Exupery

---

OO Design Quality Metrics: An Analysis of Dependencies

http://www.objectmentor.com/resources/articles/oodmetrc.pdf

Oh, Uncle Bob.. you've already done everything cool, haven't you?

kerrizor

@tectonic's notes for Kerri Miller's (@kerrizor) RailsConf 2015 talk -- http://railsconf.com/program#prop_980

Interview Day
- Set and communicate a schedule (“two-three hours, no laptop needed, we will get lunch, no need to dress up”)
- Set expectations (“we will be writing some code together”)
- Have a diverse set of interviewers
- Allow for breaks

Make a game plan
- assign areas of focus (you do SQL, I’ll do OO)

kerrizor

Step 0:

Get Homebrew installed on your mac if you don't already have it

Step 1:

Install highlight. "brew install highlight". (This brings down Lua and Boost as well)

Step 2:

kerrizor

Venue Considerations Checklist

• Facility
  • Security/Maintenence
    • Will venue provide staff person(s) day of event for coordination?
    • Who is contact point in case of problems
  • Room(s)
    • Number of individual meeting spaces
    • Capacity of each
    • Relative arrangement of rooms (are they close to each other)
• Outdoor/shared space to facilitate hallway track

kerrizor

I love movies. I love talking about movies. Let's watch movies, and then talk about them together, book club style!

Every 2-4 weeks, we'll pick a movie that is readily accessible, and pledge to watch it sometime during that interval. We'll schedule a mutually agreeable time for the end of that period and do a Google hangout, 30-60 minutes in length (longer, if we feel so motivated) to discuss and share reactions, insights, ideas, and interpretations of the film. Interested?

kerrizor

### Keybase proof

I hereby claim:

  * I am kerrizor on github.
  * I am kerrizor (https://keybase.io/kerrizor) on keybase.
  * I have a public key whose fingerprint is A605 9199 EFA5 4BBC DDC0  A6B8 B0BF C6ED 2615 9F0F

To claim this, I am signing this object: