Goto chicago

17
Jazmin Schroeder @jazschroeder GOTO Chicago 2014 The Drake

Transcript of Goto chicago

Page 1: Goto chicago

Jazmin Schroeder @jazschroeder

GOTO Chicago 2014The Drake

Page 2: Goto chicago
Page 3: Goto chicago
Page 4: Goto chicago

Speed and Scale: How to get thereAdrian Cockcroft @adrianco

- Microservices for speed and availability

- Don’t do your own undifferentiated heavy

lifting

- Culture of freedom and responsibility

- Simple patterns automated by tooling

Recommendations:

The Phoenix Project

Lean Enterprise

Page 5: Goto chicago

Following Google or don’t follow the followers

follow the leaderMark Madsen @markmadsen

- A brief history of data storage and

retrieval

- From clay to Big Data

- Is Hadoop & NoSQL the answer to your

problem?- Some people can’t resist getting the next

new thing because it’s new.

- Better to ask “What is the problem for

which technology is the answer”

Page 6: Goto chicago

Kicking the complexity habitDan North @tastapod

- Complexity is the default condition

- Simplifying is always an option

- Consistency is the key

“It really shouldn’t be this difficult”

“Familiarity is not simplicity”

Page 7: Goto chicago

DevOps Culture And Practices To Create Flow

Jez Humble @ jezhumble

- Use automation to detect

problems quickly

- Work in small batches

- Measure and improve customer

outcomes

- Use continuos improvements to

get better

TODO:

Read Lean Enterprise

Page 8: Goto chicago

What I Learned About Going Fast at eBay and Google

Randy Shoup @randyshoup

How can we make organizations

faster?

- People

- Organizational culture

- Process

“When you choose features and

a date, you implicitly choose a

level of quality”

Page 9: Goto chicago

Why we chose Cascalog for Data Processing and

Machine LearningKurt Schrader @kurt

- Word count SQL

- Word count Java Hadoop

- Word count PIG

- Word count Cascading

- And.. Word count Cascalog

“We’ll be able to write our data processing code

at a high level of abstraction and let the system

handle the complexity underneath”

Page 10: Goto chicago

Does the Browser have a Future?Tim Bray @timbray

- Server side developers have many

options

- Clojure, Scala, Erlang. GO may be the

one that takes over the world

- Front end developers face the challenge

of having to develop for multiple platforms

- What can we do to save the browser?

Page 11: Goto chicago

Scala - The Simple Parts

Martin Odersky @odersky

10 years of Scala

- Expressions

- Scopes

- Patterns and Case Classes

- Recursion

- Function Values

- Collections

- Vars

“A large system is one where you do not

know that some of

its components even exist”

Page 12: Goto chicago

Elixir: The Power of Erlang, the Joy of Ruby

Dave Thomas @pragdave

Elixir Live coding!!!

Page 13: Goto chicago

Technology Management, WTF?

Derek Groothuis @Derek Groothuis & Lyle Hayhurst @sozin

Omniscience

Policy

Incentives

Estimates

Context Switching

Email

Omnipotence

Meetings

The sword

Other managers

Lawyers

Why management can be insane?

“When things go well give credit to the team,

when things go wrong take the blame”

Page 14: Goto chicago

Controlling Physical Devices on the Real-Time Web - Enterprise Grade

WebSocket for the Internet of Things

Peter Moskovits @peterm_kaazing

- HTML5 WebSocket: TCP for the

Web- Bridging the Gap Between Hardware

and Software

- Fun Demos

“Great demos!”

Page 15: Goto chicago

The Functional Final Frontier

David Nolen @swannodette

A look at Om - - a ClojureScript

interface to Facebook's React.

“Front end is more than MVC”

Page 16: Goto chicago

Functional Principles for OO Developers

Jessica Kerr @jessitron

Principles of functional programing:

- Data In, Data Out

- Immutability

- Verbs Are People Too

- Declarative Style

- Specific Typing

- Lazy Evaluation

- Organizational culture

- Process

“Start applying functional programing

principles today”

Page 17: Goto chicago

GOTO Chicago

Thanks to the

sponsors!