globulon

(defn problem-fifty-two[]
  (time (take 1 (drop-while #(not (= 1 (count (set (map (comp sort str (partial * %)) [2 3 4 5 6]))))) (iterate inc 1)))))

kevin-smets

Default

Powerlevel10k

oakes

Contents

• Why care about Rust?
• The Toolchain
• Creating a New Project
• Modules
• Crates
• Types
• References
• Mutability

philandstuff

Kush, an introduction to schedulers

about me

• I work for GDS
• Cabinet Office
• we started by building GOV.UK
  • replaced older sites like direct gov, business link
• we’re not just fixing websites
  • we also build and run digital services
  • working with depts across the country
  • eg: register to vote

tzachz

package com.kenshoo.kripke.core

import com.yammer.metrics.Metrics
import com.yammer.metrics.core.{MetricName, Counter}
import org.apache.spark.Accumulator
import org.apache.spark.rdd.RDD

import scala.reflect.ClassTag

object CounterBackedAccumulatorUtil {

edwthomas

(:require [re-frame.core :as re-frame]
          [reagent.core :as reagent]
          [cljsjs.chartjs])
          
(defn show-revenue-chart
  []
  (let [context (.getContext (.getElementById js/document "rev-chartjs") "2d")
        chart-data {:type "bar"
                    :data {:labels ["2012" "2013" "2014" "2015" "2016"]
                           :datasets [{:data [5 10 15 20 25]

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

kbilsted

Moved to https://github.com/kbilsted/Functional-core-imperative-shell/blob/master/README.md

reborg

Rich Already Answered That!

A list of commonly asked questions, design decisions, reasons why Clojure is the way it is as they were answered directly by Rich (even when from many years ago, those answers are pretty much valid today!). Feel free to point friends and colleagues here next time they ask (again). Answers are pasted verbatim (I've made small adjustments for readibility, but never changed a sentence) from mailing lists, articles, chats.

How to use:

• The link in the table of content jumps at the copy of the answer on this page.
• The link on the answer itself points back at the original post.

Table of Content

sroccaserra

L'Après-midi du DDD

2017-06-07

Mes notes brutes sur l'après-midi du DDD :)

Merci à @tpierrain, @brunoboucard, @jgrodziski, Microsoft,