marioaquino

#System Design Cheatsheet

Picking the right architecture = Picking the right battles + Managing trade-offs

##Basic Steps

1. Clarify and agree on the scope of the system

• User cases (description of sequences of events that, taken together, lead to a system doing something useful)
  • Who is going to use it?
  • How are they going to use it?

marioaquino

For each Ruby module/class, we have Ruby methods on the left and the equivalent
Clojure functions and/or relevant notes are on the right.

For clojure functions, symbols indicate existing method definitions, in the 
clojure namespace if none is explicitly given.  clojure.contrib.*/* functions can
be obtained from http://github.com/kevinoneill/clojure-contrib/tree/master,
ruby-to-clojure.*/* functions can be obtained from the source files in this
gist.

If no method symbol is given, we use the following notation:

marioaquino

class GroupOfThingies
  attr_accessor :thingies

  # Use like this:
  #
  #   group_of_thingies = GroupOfThingies.new
  #   group_of_thingies.each do |thing|
  #     puts "Check out this awesome thing: #{thing}!"
  #   end
  #

marioaquino

(1..100).each do |num|
  out = num % 3 == 0 ? 'Fizz' : ''
  out << 'Buzz' if num % 5 == 0
  out = num if out.size == 0
  print out
end