daveshah

##Some quick thoughts on tracking happiness I've done this with a couple of teams. I've used Mercury App and Google Forms.

Some things I've learned from this:

• Setting expectations is important - we're going to have good and bad days - that's okay. That's human.
• It's important to PAY ATTENTION and HONESTLY AND OPENLY discuss the reasons we're happy / unhappy. (make sure there's room for notes)
• It's important to remember balance - making one group happy can easily make another one unhappy. Be mindful of the impact of our actions in a larger context!
• IMO, as with all metrics, this is one the team should own.
• This definitely takes discipline. It's easy to forget to track things. Try and set a calendar reminder (or similiar) to take 5 minutes or so and keep this habit.

daveshah

BiggestSlacker.Slack.channels 
|> Enum.take(10) 
|> Enum.map(&{&1.id, &1.name}) 
|> Enum.map(fn({id, name}) -> {name, BiggestSlacker.Slack.channel_history(id)} end) 
|> Enum.map(fn({name, hist_map}) -> {name, BiggestSlacker.Stats.users_to_message_counts(hist_map.messages)} end) 
|> Enum.map(fn({name,list}) -> {name, Enum.at(list,0)} end)

daveshah

 def "Loading into the solr core"() {

        given: "An empty solr core"
        def solrServer = new EmbeddedSolrServer(Paths.get("../solr"), "corename")

        when: "I load the core"
        def params = new ModifiableSolrParams(){{
            add("command","full-import")
            add("clean","true")
            add("commit","true")

daveshah

require 'fileutils'

class Tuple
	attr_accessor :first, :last
	def	initialize(first,last)
		@first = first
		@last = last
	end
end

daveshah

package com.lolz;

public class AwesomeSauce {

    {
        // Note that the interface is package protected so trying to access these outside the
        // package is no-bueno!
        Foo.Bar bar = new Foo.Bar();
        Foo.Baz baz = new Foo.Baz();

daveshah

function setjdk() {
  if [ $# -ne 0 ]; then
	removeFromPath '/System/Library/Frameworks/JavaVM.framework/Home/bin'
	if [ -n "${JAVA_HOME+x}" ]; then
	removeFromPath $JAVA_HOME
	fi
	export JAVA_HOME=`/usr/libexec/java_home -v $@`
	export PATH=$JAVA_HOME/bin:$PATH
	fi
}

daveshah

#!/usr/local/bin/scala
::#!
@echo off
scala %0 %*
goto :eof
::!#

println("Hello Dave")

daveshah

A few years back I was pairing with a developer who passed on a really good habit of jotting down thoughts as we paired. We'd always have a stack of post-it notes by our side and as we'd navigate through the code base focused on our current task and test, we'd take note of things that needed to be cleaned.

The interesting thing I noticed about this - sometimes these notes would give us the breadcrumb trail we needed to get right back on track.

Every developer worth their salt should try and live by the boyscout rule. In a big forest of a codebase, it's easy to start tidying up far from the original spot we initially want to start cleaning.

Before you know it, you're in some strange part of the codebase you've never been before and you may ask yourself... how did I get here.

The post-its and scratch pads always kept us from getting lost. They always gave us a way back. We'd jot down o

daveshah

case class Person(id: Int,firstName: String, lastName: String)

object  PersonRepository {

  private val people = Map(
    1 -> Person(1,"Shah","Dave"),
    2 -> Person(2,"Barington","Foo")
  )

daveshah

#!/bin/bash
defaults write com.apple.finder AppleShowAllFiles YES