richhickey

;annotation syntax

(import [java.lang.annotation Retention RetentionPolicy Target ElementType]
        [javax.xml.ws WebServiceRef WebServiceRefs])
(definterface Foo (foo []))

;annotation on type
(deftype ^{Deprecated true 
            Retention RetentionPolicy/RUNTIME 
            javax.annotation.processing.SupportedOptions ["foo" "bar" "baz"]

michiakig

;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;; Ant sim ;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;   Copyright (c) Rich Hickey. All rights reserved.
;   The use and distribution terms for this software are covered by the
;   Common Public License 1.0 (http://opensource.org/licenses/cpl.php)
;   which can be found in the file CPL.TXT at the root of this distribution.
;   By using this software in any fashion, you are agreeing to be bound by
;   the terms of this license.
;   You must not remove this notice, or any other, from this software.

;dimensions of square world

ihercowitz

import sys

def prime(number):
    n = abs(number)

    if n < 1:
        return False

    if n==2:
        return True

tapajos

Migrando do Heroku para a Amazon Web Services

Recentemente eu comentei sobre a migração que fizemos no [Myfinance][mf] saindo do [Heroku][h] e indo para a [Amazon Web Services][a] e diversas pessoas me perguntaram as razões pela qual fizemos essa mudança. O objetivo desse post é apenas explicar a decisão que a nossa equipe tomou, como foi e as conseguências dessa migração.

Antes de começar eu gostaria de deixar claro que o objetivo desse texto não é comparar hospedagens e nem dizer que uma é melhor do que a outra. Trata-se apenas do relato de uma experiência.

A motivação

Antes de explicar a motivação por trás da migração é interessante mostrar como era a nossa estrutura.

diegopacheco

Software Architecture Resources

Tech / Approach / Def.

http://www.bredemeyer.com/links.htm
http://perfwork.wordpress.com/
http://blog.8thlight.com/uncle-bob/2012/08/13/the-clean-architecture.html
http://en.wikipedia.org/wiki/4%2B1_architectural_view_model
http://epf.eclipse.org/wikis/openup/core.tech.common.extend_supp/guidances/examples/four_plus_one_view_of_arch_9A93ACE5.html

ptaoussanis

(comment ; Fun with transducers, v2

  ;; Still haven't found a brief + approachable overview of Clojure 1.7's new
  ;; transducers in the particular way I would have preferred myself - so here goes:

  ;;;; Definitions
  ;; Looking at the `reduce` docstring, we can define a 'reducing-fn' as:
  (fn reducing-fn ([]) ([accumulation next-input])) -> new-accumulation
  ;; (The `[]` arity is actually optional; it's only used when calling
  ;; `reduce` w/o an init-accumulator).

diegopacheco

{ :FP, :FRP, :Streams, :MapReduce, :Batch }

• Reactive Manifesto 2.0 -> http://www.reactivemanifesto.org/
• Akka -> http://akka.io/
• Spray.io -> http://spray.io/
• Functional Programing -> http://learnyouahaskell.com/chapters
• Streams -> http://www.reactive-streams.org/
• Spark -> http://spark.apache.org/
• Samza -> http://samza.incubator.apache.org/

wojteklu

Code is clean if it can be understood easily – by everyone on the team. Clean code can be read and enhanced by a developer other than its original author. With understandability comes readability, changeability, extensibility and maintainability.

---

General rules

1. Follow standard conventions.
2. Keep it simple stupid. Simpler is always better. Reduce complexity as much as possible.
3. Boy scout rule. Leave the campground cleaner than you found it.
4. Always find root cause. Always look for the root cause of a problem.

Design rules