Slide 1

Slide 1 text

The Life & Death of a Rails App

Slide 2

Slide 2 text

SPOILER

Slide 3

Slide 3 text

We are all going to die.

Slide 4

Slide 4 text

404

Slide 5

Slide 5 text

No content

Slide 6

Slide 6 text

No content

Slide 7

Slide 7 text

The Life and Death of a Rails App Olivier

Slide 8

Slide 8 text

No content

Slide 9

Slide 9 text

No content

Slide 10

Slide 10 text

Birth

Slide 11

Slide 11 text

Late 2010 Orlando, Florida

Slide 12

Slide 12 text

$ rails new app

Slide 13

Slide 13 text

$ rails new app\ -d postgresql --skip-test-unit --skip-spring --skip-javascript

Slide 14

Slide 14 text

No content

Slide 15

Slide 15 text

No content

Slide 16

Slide 16 text

2f0e7c9f1c 2010-12-22 Initial Commit. [Andrew Smith]

Slide 17

Slide 17 text

Jan 2012 Orlando, Florida

Slide 18

Slide 18 text

No content

Slide 19

Slide 19 text

53ff7c4bab 2012-01-19 Specifying that group subscriptions are per seat. [Olivier Lacan]

Slide 20

Slide 20 text

4a59521d5e 2013-05-24 I'm a fucking idiot. [Olivier Lacan]

Slide 21

Slide 21 text

Barriers to Entry

Slide 22

Slide 22 text

No content

Slide 23

Slide 23 text

No content

Slide 24

Slide 24 text

audience * ) timing + content (

Slide 25

Slide 25 text

No content

Slide 26

Slide 26 text

No content

Slide 27

Slide 27 text

$ git push heroku master

Slide 28

Slide 28 text

No content

Slide 29

Slide 29 text

No content

Slide 30

Slide 30 text

No content

Slide 31

Slide 31 text

gem "this" gem "that" gem "also_this" gem "why_not" gem "all_the_things" gem "omfg"

Slide 32

Slide 32 text

Dependencies Software

Slide 33

Slide 33 text

Dependencies Human

Slide 34

Slide 34 text

Adolescence

Slide 35

Slide 35 text

"Let's do Ops to save money!"

Slide 36

Slide 36 text

No content

Slide 37

Slide 37 text

No content

Slide 38

Slide 38 text

Opportunity Cost noun Economics the loss of potential gain from other alternatives when one alternative is chosen.

Slide 39

Slide 39 text

Heroku In-house $5,000/month $3,000/month + payroll + vacation + security + upgrades + turnover = /month

Slide 40

Slide 40 text

Not Invented Here

Slide 41

Slide 41 text

"GitHub made their own support app!"

Slide 42

Slide 42 text

"Why shouldn't we..."

Slide 43

Slide 43 text

"We're special too, right?"

Slide 44

Slide 44 text

(wrong)

Slide 45

Slide 45 text

Users Authorization Admin Jobs Billing Servers Security Browsers Database Emails Etc.

Slide 46

Slide 46 text

$ rails new tool $ rails new other_tool $ rails new best_tool $ rails new micro_service $ rails new macro_service $ mix phx.new ruby_3x3 $ express async_all_the_things

Slide 47

Slide 47 text

No content

Slide 48

Slide 48 text

Security upgrades Ruby upgrades Rails upgrades Documentation ) ( x 103

Slide 49

Slide 49 text

require "active_model/railtie" require "active_job/railtie" # require "active_record/railtie" require "action_controller/railtie" require "action_mailer/railtie" require "action_view/railtie" require "action_cable/engine" require "sprockets/railtie" require "rails/test_unit/railtie"

Slide 50

Slide 50 text

Justify our Difference

Slide 51

Slide 51 text

$ hanami new so_fresh_so_clean $ dry-web-roda new dry_FTW

Slide 52

Slide 52 text

Rails Freedom

Slide 53

Slide 53 text

Easy Simple

Slide 54

Slide 54 text

Big Small

Slide 55

Slide 55 text

Yes Maybe

Slide 56

Slide 56 text

Rails is a siphon for good ideas.

Slide 57

Slide 57 text

Rails Ruby on

Slide 58

Slide 58 text

cross-pollination ✨ ✨

Slide 59

Slide 59 text

Data Mapper CarrierWave Capybara Sequel Sidekiq RSpec

Slide 60

Slide 60 text

ActiveRecord ActiveStorage System Tests Arel ActiveJob MiniTest::Spec

Slide 61

Slide 61 text

Architecture

Slide 62

Slide 62 text

app/ vs lib/ 2010

Slide 63

Slide 63 text

app/models vs app/services 2013

Slide 64

Slide 64 text

Rails and SOA: Do I really need 
 to have this big app? December 26, 2013 Developing complex web applications (not particularly Rails apps) is a tricky task. You write your models, controllers, services and optimize application architecture iteratively. But even with the great architecture when your application starts to be huge, bad things happen. Every little feature you’ll add will cost you precious time - tests must pass on your CI and workers needs to be reloaded every time you deploy. In addition, you begin to realize that mental overhead with keeping modules separated is huge - you have to remember a lot of things to keep it in right fashion. Ultimately, working on a project is hard, TDD technique is inefficient to use and you’re not happy at all with your code.

Slide 65

Slide 65 text

SOA

Slide 66

Slide 66 text

No content

Slide 67

Slide 67 text

Service-oriented Architecture

Slide 68

Slide 68 text

Business activity with outcome.
 Self-contained.
 Black box for consumers.
 May consist of other underlying services.

Slide 69

Slide 69 text

Local complexity vs. Perpetual inconsistency

Slide 70

Slide 70 text

Localized SOA

Slide 71

Slide 71 text

app/models + app/services

Slide 72

Slide 72 text

No content

Slide 73

Slide 73 text

User.create + CreateUser.new

Slide 74

Slide 74 text

No content

Slide 75

Slide 75 text

CreateUser SubscribeUser ChargeSubscription

Slide 76

Slide 76 text

Unexpected Paths

Slide 77

Slide 77 text

CreateUser ChargeSubscription SubscribeUser

Slide 78

Slide 78 text

Charge.create User.create Subscription.create CreateUser ChargeSubscription SubscribeUser

Slide 79

Slide 79 text

No content

Slide 80

Slide 80 text

“What if…”

Slide 81

Slide 81 text

Adulthood

Slide 82

Slide 82 text

Experiment Side-project Product

Slide 83

Slide 83 text

(In)stability Teammate

Slide 84

Slide 84 text

Ownership Lack of

Slide 85

Slide 85 text

No content

Slide 86

Slide 86 text

+

Slide 87

Slide 87 text

Diversity

Slide 88

Slide 88 text

No content

Slide 89

Slide 89 text

No content

Slide 90

Slide 90 text

No content

Slide 91

Slide 91 text

Immunity

Slide 92

Slide 92 text

Distrust
 the Process

Slide 93

Slide 93 text

Beware of Bibles

Slide 94

Slide 94 text

“During the gold rush its a good time to be in the pick and shovel business” Probably Not Mark Twain

Slide 95

Slide 95 text

No content

Slide 96

Slide 96 text

Shovel-as-a-Service

Slide 97

Slide 97 text

Use Make vs.

Slide 98

Slide 98 text

Scalability

Slide 99

Slide 99 text

504

Slide 100

Slide 100 text

HTTP Status 504 The server, while acting as a gateway or proxy, did not receive a timely response from an upstream server it needed to access in order to complete the request.

Slide 101

Slide 101 text

whoops

Slide 102

Slide 102 text

No content

Slide 103

Slide 103 text

No content

Slide 104

Slide 104 text

No content

Slide 105

Slide 105 text

Rails can scale.

Slide 106

Slide 106 text

No content

Slide 107

Slide 107 text

JavaScript however...

Slide 108

Slide 108 text

(okay, my JavaScript)

Slide 109

Slide 109 text

No content

Slide 110

Slide 110 text

No content

Slide 111

Slide 111 text

Performance is hard work.

Slide 112

Slide 112 text

People are even harder work.

Slide 113

Slide 113 text

Devalue Code Overvalue People

Slide 114

Slide 114 text

No content

Slide 115

Slide 115 text

Software Developer Bulldozer

Slide 116

Slide 116 text

Security

Slide 117

Slide 117 text

“Who has credentials for the MailChimp account?”

Slide 118

Slide 118 text

“Peter, he left the company two months ago.”

Slide 119

Slide 119 text

No content

Slide 120

Slide 120 text

+

Slide 121

Slide 121 text

Hey! Thank you for the message As I said I have found several SERIOUS security vulnerabilities; so I want to ask you if you can make a "team" on hackerone.com . It's a platform where security researchers report vulnerabilities to company.

Slide 122

Slide 122 text

No content

Slide 123

Slide 123 text

No content

Slide 124

Slide 124 text

No content

Slide 125

Slide 125 text

Bug Bounty Security Program

Slide 126

Slide 126 text

Researcher Reputation Reward Guidance Attract White Hats +

Slide 127

Slide 127 text

Security through "lalala not listening" is not security.

Slide 128

Slide 128 text

Privacy

Slide 129

Slide 129 text

G.D.P.R.

Slide 130

Slide 130 text

General Data Protection Regulation

Slide 131

Slide 131 text

How GDPR Will Change 
 The Way You Develop Europe’s imminent privacy overhaul means that we all have to become more diligent about what data we collect, how we collect it, and what we do with it. In our turbulent times, these privacy obligations are about ethics as well as law. Web developers have a major role to play here. After all, healthy data protection practice is as much about the development side — code, data, and security — as it is about the business side of process, information, and strategy.

Slide 132

Slide 132 text

P.I.I

Slide 133

Slide 133 text

No content

Slide 134

Slide 134 text

Personally identifiable information Personal information, described in United States legal fields as either personally identifiable information (PII), or sensitive personal information (SPI), as used in information security and privacy laws, is information that can be used on its own or with other information to identify, contact, or locate a single person, or to identify an individual in context.

Slide 135

Slide 135 text

According to the European Commission, "personal data is any information relating to an individual, whether it relates to his or her private, professional or public life. It can be anything from a name, a home address, a photo, an email address, bank details, posts on social networking websites, medical information, or a computer’s IP address."

Slide 136

Slide 136 text

Devise Rails

Slide 137

Slide 137 text

•Trackable: tracks sign in count, timestamps and IP address.

Slide 138

Slide 138 text

create_table "users", force: :cascade do |t| t.text "name" t.string "email" t.datetime "created_at" t.datetime "updated_at" t.datetime "current_sign_in_at" t.datetime "last_sign_in_at" t.string "country_code" t.string "current_sign_in_ip" t.string "encrypted_password" t.string "last_sign_in_ip" end

Slide 139

Slide 139 text

Are you GDRP- compliant?

Slide 140

Slide 140 text

https://www.reddit.com/r/rails/comments/885ufz/gdpr_rails_are_you_doing_anything_to_prepare/

Slide 141

Slide 141 text

No content

Slide 142

Slide 142 text

Who owns user data?

Slide 143

Slide 143 text

Where does the data go when it's over?

Slide 144

Slide 144 text

Retirement

Slide 145

Slide 145 text

No content

Slide 146

Slide 146 text

Three years later…

Slide 147

Slide 147 text

No content

Slide 148

Slide 148 text

Death

Slide 149

Slide 149 text

No content

Slide 150

Slide 150 text

No content

Slide 151

Slide 151 text

The sun comes back after a sunset.

Slide 152

Slide 152 text

No content

Slide 153

Slide 153 text

Startup

Slide 154

Slide 154 text

Emotional honesty

Slide 155

Slide 155 text

We are shutting Code School down forever.

Slide 156

Slide 156 text

It fucking hurts.

Slide 157

Slide 157 text

Its spirit lives on in Pluralsight. But it still hurts.

Slide 158

Slide 158 text

No content

Slide 159

Slide 159 text

20%

Slide 160

Slide 160 text

2011 - 2018 Code School

Slide 161

Slide 161 text

Post-Mortem

Slide 162

Slide 162 text

Are legacy apps our legacy?

Slide 163

Slide 163 text

No.

Slide 164

Slide 164 text

It's people.

Slide 165

Slide 165 text

Ditch Toxic People

Slide 166

Slide 166 text

Nurture Good People

Slide 167

Slide 167 text

Share Ownership

Slide 168

Slide 168 text

The product.

Slide 169

Slide 169 text

Get Involved

Slide 170

Slide 170 text

Accept Mortality

Slide 171

Slide 171 text

The ideas.

Slide 172

Slide 172 text

Share Healthy Habits

Slide 173

Slide 173 text

Focus on Joy

Slide 174

Slide 174 text

Learn by Doing

Slide 175

Slide 175 text

Just in Time Learning

Slide 176

Slide 176 text

Merci.

Slide 177

Slide 177 text

@olivierlacan

Slide 178

Slide 178 text

No content

Slide 179

Slide 179 text

Questions? Come chat in the hall.