I hereby claim:
- I am dnch on github.
- I am dc (https://keybase.io/dc) on keybase.
- I have a public key whose fingerprint is FDDA F1C8 3DB1 F33E F831 5A5C EACC B946 5AE3 1ED7
To claim this, I am signing this object:
Gross Income A = 180,200 | |
Deductions A = 0 | |
Taxable Income A = Gross Income A - Deductions A => 180,200 | |
Tax Liability A = 54,547 + (0.45 * (Taxable Income A - 180000)) => 54,637 | |
Gross Income B = 180,200 | |
Deductions B = 300 | |
Taxable Income B = Gross Income B - Deductions B => 179,900 | |
Tax Liability B = 17,547 + (0.37 * (Taxable Income B - 80000)) => 54,510 |
module Derp | |
def derp | |
puts "Derp" | |
end | |
end |
I hereby claim:
To claim this, I am signing this object:
- content_for :sidebar do | |
.make_me_purple | |
derp derp derp derp derp derp derp derp derp derp derp derp derp derp derp derp |
I hereby claim:
To claim this, I am signing this object:
// BAD IDEA: Not enforcing any sorts of rules about how packages are composed. | |
// | |
// Bower allows developers to override certain properties of each package's bower | |
// definition. Which is handy when packages are badly composed. | |
// | |
// In everyone's defence, Bower is still relatively new and given that there's a | |
// seemingly infinite number of ways to get to the end-point, there really is no | |
// right or wrong way to do it. | |
// | |
"overrides": { |
Greetings folks,
I’m the development manager for The Full Circle Group (www.fullcirclegroup.com.au). We’ve got a SaaS platform that specialises in telecommunications analytics, auditing, and expense management. Think Google Analytics, but for your phone bill.
We’re looking for a permanent, full-time Rails+JavaScript developer to join our team. We have two well-established, constantly-evolving apps that form the core of our business, and we're also in the early build stages of another, brand new app (based on Ruby 2/Rails 4).
We’re not looking for experience in any specific areas beyond a strong understanding of Ruby on Rails and modern JavaScript development techniques. You don’t need be a guru or a wizard— we want to build a team with a broad set of skills and the ability to dive in and help us out with the following:
describe Dekor::Base do | |
it "in an act of cowardice, refuses to self-instantiate under its own guise" do | |
end | |
it "demands a sacrifice to the Object lord" do | |
end | |
it "has a possee, just like Andre The Giant" do | |
end |
#!/usr/bin/env ruby -w | |
class Derp | |
@exportable = [] | |
class << self | |
def exportable(meth) | |
@exportable << meth | |
end | |
def exportable_methods |
require 'spec_helper' | |
describe API::Decorator do | |
describe ".safe_attributes" do | |
# class WidgetDecorator < API::Decorator | |
# safe_attributes :safe | |
# end | |
# | |
# widget = Widget.new(safe: "foo", unsafe: "bar") | |
# |