Sustainable Productivity: Rails vs OOP

Slide 1

Slide 1 text

4VTUBJOBCMF 1SPEVDUJWJUZ 3BJMTWT001

Slide 2

Slide 2 text

"UUIF CFHJOOJOH

Slide 3

Slide 3 text

No content

Slide 4

Slide 4 text

&3# 5FTU6OJU .Z42-

Slide 5

Slide 5 text

BLB 5IF (PMEFO 1BUI 5IF 3BJMT 8BZ

Slide 6

Slide 6 text

,*44

Slide 7

Slide 7 text

%3:

Slide 8

Slide 8 text

4LJOOZ$POUSPMMFST 'BU.PEFMT http://weblog.jamisbuck.org/2006/10/18/skinny-controller-fat-model

Slide 9

Slide 9 text

http://flic.kr/p/88SDCu

Slide 10

Slide 10 text

http://flic.kr/p/88JHir

Slide 11

Slide 11 text

http://flic.kr/p/88MWyf

Slide 12

Slide 12 text

4J[F $PNQMFYJUZ

Slide 13

Slide 13 text

)BNM 34QFD $VDVNCFS 1PTUHSF42- 1SFTFOUFST 4FSWJDFT $PODFSOT 3PMFT %$* .PDLT )FYBHPOBM %%% &3# 5FTU6OJU .Z42- $P⒎F4DSJQU

Slide 14

Slide 14 text

4IPVMEXFEFWJBUF GSPNUIF(PMEFO 1BUIUPEP001 SJHIU

Slide 15

Slide 15 text

8IBUBSFUIF CFOFpUTPGVTJOH UIBUQBUUFSOPSUIBU UFDIOJRVF

Slide 16

Slide 16 text

8IBUBSFUIF QJUGBMMT

Slide 17

Slide 17 text

/P TJOHMF BOTXFS

Slide 18

Slide 18 text

$PIFTJPO$PVQMJOH 40-*%QSJODJQMFT %BUBWT3FTQPOTJCJMJUZ $FSFNPOZWT&TTFODF 5IFDPTUPGJOEJSFDUJPO 3BJMTWT001

Slide 19

Slide 19 text

$PIFTJPO $PVQMJOH

Slide 20

Slide 20 text

$MBTTJD 4PGUXBSF $PODFQUT

Slide 21

Slide 21 text

#JH"DUJWF3FDPSE NPEFMTIBWFMPX DPIFTJPO

Slide 22

Slide 22 text

!!class!Article!

Slide 23

Slide 23 text

!!class!Article!!Forem.user_class.to_s !!!!belongs_to!:reply_to,!:class_name!=>!"Post" ! !!!!has_many!:replies,!:class_name!!=>!"Post", !!!!!!!!!!!!!!!!!!!!!!!:foreign_key!=>!"reply_to_id", !!!!!!!!!!!!!!!!!!!!!!!:dependent!!!=>!:nullify !!!! !!!!has_many!:taggings !!!!has_many!:tags,!:through!=>!:taggings ! !!!!validates!:text,!:presence!=>!true ! !!!!delegate!:forum,!:to!=>!:topic ! !!!!after_create!:set_topic_last_post_at !!!!after_create!:skip_pending_review !!!!after_save!:email_topic_subscribers ! !!!!class!<!'pending_review' !!!!!!end ! !!!!!!def!spam !!!!!!!!where!:state!=>!'spam' !!!!!!end !!!!!! !!!!!!def!tagged_with(tag) !!!!!!!!joins(:taggings!=>!:tags).where(:tags!=>!{!:name!=>!tag!}) !!!!!!end ! !!!!!!def!visible !!!!!!!!joins(:topic).where(:forem_topics!=>!{!:hidden!=>!false!}) !!!!!!end !!!!end !!!! !!!!def!tag_names=(tag_list) !!!!!!assign_tag_list!tag_list !!!!end ! !!!!private ! !!!!def!subscribe_replier !!!!!!if!topic!&&!user !!!!!!!!topic.subscribe_user(user.id) !!!!!!end !!!!end ! !!!!def!set_topic_last_post_at !!!!!!topic.update_attribute(:last_post_at,!created_at) !!!!end ! !!!!def!blacklist_user !!!!!!user.update_attribute(:forem_state,!"spam")!if!user !!!!end !!!! !!!!def!assign_tag_list(tag_list) !!!!!!tag_names!=!tag_list.gsub(/\s+/,!"").split(",") !!!!!!existing!=!self.tags.map!{|t|!t.name!} !!!!!!(existing!@!tag_names).each!do!|name| !!!!!!!!self.tags.delete!Tag.find_by_name(name) !!!!!!end !!!!!!tag_names.each!do!|name| !!!!!!!!self.tags!<

Slide 24

Slide 24 text

!!!belongs_to!:user,!!!!!:class_name!=>!Fore !!!belongs_to!:reply_to,!:class_name!=>!"Pos !!!has_many!:replies,!:class_name!!=>!"Post" !!!!!!!!!!!!!!!!!!!!!!:foreign_key!=>!"reply !!!!!!!!!!!!!!!!!!!!!!:dependent!!!=>!:nulli !!! !!!has_many!:taggings !!!has_many!:tags,!:through!=>!:taggings !!!validates!:text,!:presence!=>!true !!!delegate!:forum,!:to!=>!:topic !!!after_create!:set_topic_last_post_at !!!after_create!:skip_pending_review

Slide 25

Slide 25 text

!!!!end !!!!def!pending_review !!!!!!where!:state!=>!'pending_review' !!!!end !!!!def!spam !!!!!!where!:state!=>!'spam' !!!!end !!!! !!!!def!tagged_with(tag) !!!!!!joins(:taggings!=>!:tags).where(:tags!=>!{!:name!=>!tag!}) !!!!end !!!!def!visible !!!!!!joins(:topic).where(:forem_topics!=>!{!:hidden!=>!false!}) !!!!end !!end !! !!def!tag_names=(tag_list) !!!!assign_tag_list!tag_list !!end !!private

Slide 26

Slide 26 text

!!!!!end !!!end !!! !!!def!tag_names=(tag_list) !!!!!assign_tag_list!tag_list !!!end !!!private !!!def!subscribe_replier !!!!!if!topic!&&!user

Slide 27

Slide 27 text

! !!!!def!blacklist_user !!!!!!user.update_attribute(:forem_state,!"spam")!if!user !!!!end !!!! !!!!def!assign_tag_list(tag_list) !!!!!!tag_names!=!tag_list.gsub(/\s+/,!"").split(",") !!!!!!existing!=!self.tags.map!{|t|!t.name!} !!!!!!(existing!@!tag_names).each!do!|name| !!!!!!!!self.tags.delete!Tag.find_by_name(name) !!!!!!end !!!!!!tag_names.each!do!|name| !!!!!!!!self.tags!<

Slide 28

Slide 28 text

Slide 29

Slide 29 text

r.BSUJO'PXMFS l1VUUPHFUIFS XIBUDIBOHFT UPHFUIFSz

Slide 30

Slide 30 text

class!Article!

Slide 31

Slide 31 text

module!Taggable !!extend!ActiveSupport::Concern !!included!do !!!!has_many!:taggings !!!!has_many!:tags,!through:!:taggings !!!!scope!:tagged_with,!1>(tag_name)!do !!!!!!joins(:tags).where(tags:!{!name:!tag_name!})! !!!!end !!end !!def!tag_list !!!!tags.pluck(:name).join(',!') !!end !!def!tag_list=(tag_list) !!!!assign_tag_list!tag_list !!end !!private !!def!assign_tag_list(tag_list) !!!!tag_names!=!tag_list.split(',').map(&:strip).uniq !!!!self.tags!=!tag_names.map!do!|tag_name|! !!!!!!Tag.where(name:!tag_name).first_or_initialize !!!!end !!end end

Slide 32

Slide 32 text

$PVQMJOH

Slide 33

Slide 33 text

$PIFTJPO 1VUUPHFUIFSXIBU DIBOHFTUPHFUIFS

Slide 34

Slide 34 text

$PVQMJOH ,FFQTFQBSBUFE XIBUEPFTO`UDIBOHF UPHFUIFS

Slide 35

Slide 35 text

http://www.flickr.com/photos/martintaylor/2301776382/

Slide 36

Slide 36 text

ActiveRecord::Base

Slide 37

Slide 37 text

%PNBJOMPHJDBOE 1FSTJTUFODFBSF UJHIUMZDPVQMFE

Slide 38

Slide 38 text

40-*% 1SJODJQMFT

Slide 39

Slide 39 text

4JOHMF3FTQPOTJCJMJUZ1SJODJQMF 0QFO$MPTFE1SJODJQMF -JTLPW4VCTUJUVUJPO1SJODJQMF *OUFSGBDF4FHSFHBUJPO1SJODJQMF %FQFOEFODZ*OWFSTJPO1SJODJQMF http://butunclebob.com/ArticleS.UncleBob.PrinciplesOfOod

Slide 40

Slide 40 text

No content

Slide 41

Slide 41 text

4JOHMF 3FTQPOTJCJMJUZ 1SJODJQMF

Slide 42

Slide 42 text

8IBUJTB SFTQPOTJCJMJUZ

Slide 43

Slide 43 text

r6ODMF#PC l"SFBTPOGPS DIBOHFz

Slide 44

Slide 44 text

109 ________________________ 8 ________________________ SRP: The Single Responsibility Principle None but Buddha himself must take the responsibility of giving out occult secrets... — E. Cobham Brewer 1810–1897. Dictionary of Phrase and Fable. 1898. This principle was described in the work of Tom DeMarco1 and Meilir Page-Jones2. They called it cohesion. They defined cohesion as the functional relatedness of the elements of a 1. [DeMarco79], p310 2. [PageJones88], Chapter 6, p82. https://docs.google.com/file/d/0ByOwmqah_nuGNHEtcU5OekdDMkk/edit

Slide 45

Slide 45 text

No content

Slide 46

Slide 46 text

149 ________________________ 9 ________________________ SRP: The Single Responsibility Principle None but Buddha himself must take the responsibility of giving out occult secrets... — E. Cobham Brewer 1810–1897. Dictionary of Phrase and Fable. 1898. This principle was described in the work of Tom DeMarco1 and Meilir Page-Jones2. They called it cohesion. As we’ll see in Chapter 21, we have a more specific definition of cohesion at the package level. However, at the class level the definition is similar. SRP: The Single Responsibility Principle THERE SHOULD NEVER BE MORE THAN ONE REASON FOR A CLASS TO CHANGE. Consider the bowling game from Chapter 6. For most of its development the Game class was handling two separate responsibilities. It was keeping track of the current frame, and it was calculating the score. In the end, RCM and RSK separated these two responsibilities into two classes. The Game kept the responsibility to keep track of frames, and the Scorer got the responsibility to calculate the score. (see page 85.) 1. [DeMarco79], p310 2. [PageJones88], Chapter 6, p82. http://www.objectmentor.com/resources/articles/srp.pdf

Slide 47

Slide 47 text

tomed to thinking of responsibility in groups. For exampl in Listing 9-1. Most of us will agree that this interface look functions it declares are certainly functions belonging to a However, there are two responsibilities being shown connection management. The second is data communicatio tions manage the connection of the modem, while the send cate data. Listing 9-1 Modem.java -- SRP Violation interface Modem { public void dial(String pno); public void hangup(); public void send(char c); public char recv(); }

Slide 48

Slide 48 text

However, there are two responsibilities being sho onnection management. The second is data communic ons manage the connection of the modem, while the s te data. Should these two responsibilities be separated? A wo sets of functions have almost nothing in common. nt reasons. Moreover, they will be called from compl ons that use them. Those different parts will change fo }

Slide 49

Slide 49 text

ng shown here. The first responsibility is munication. The dial and hangup func- e the send and recv functions communi- ated? Almost certainly they should. The mmon. They’ll certainly change for differ- completely different parts of the applica- ange for different reasons as well.

Slide 50

Slide 50 text

However, there are two responsibilities being show connection management. The second is data communica tions manage the connection of the modem, while the se cate data. Should these two responsibilities be separated? Tha tion is changing. If the application changes in ways that a tion functions, then the design will smell of Rigidity b public void Dial(string pno); public void Hangup(); public void Send(char c); public char Recv(); } Listing 8-1 (Continued) Modem.cs -- SRP Violation

Slide 51

Slide 51 text

However, there are two responsibilities being sho onnection management. The second is data communi ons manage the connection of the modem, while the s ate data. Should these two responsibilities be separated? T on is changing. If the application changes in ways tha on functions, then the design will smell of Rigidity nd read will have to be recompiled and redeployed m e two responsibilities should be separated as shown pplications from coupling the two responsibilities.

Slide 52

Slide 52 text

However, there are two responsibilities being shown here. The first responsibility is connection management. The second is data communication. The dial and hangup functions manage the connection of the modem, while the send and recv functions communi- cate data. Should these two responsibilities be separated? That depends upon how the application is changing. If the application changes in ways that affect the signature of the connection functions, then the design will smell of Rigidity because the classes that call send and read will have to be recompiled and redeployed more often than we like. In that case the two responsibilities should be separated as shown in Figure 8-3. This keeps the client applications from coupling the two responsibilities. public void Dial(string pno); public void Hangup(); public void Send(char c); public char Recv(); } Modem.cs -- SRP Violation + send(:char) + recv() : char Data Channel + dial(pno : String) + hangup() Connection «interface» «interface» WAT!

Slide 53

Slide 53 text

l"MNPTUDFSUBJOMZz

Slide 54

Slide 54 text

l*UEFQFOETz

Slide 55

Slide 55 text

%PHNB1SBHNB

Slide 56

Slide 56 text

If, on the other hand, the application is not changing in ways that cause the the two responsibilities to change at differen times, then there is no need to separate them. Indeed, separating them would smell of Needless Complexity. There is a corrolary here. An axis of change is only an axis of change if the changes actually occurr. It is not wise to apply the SRP, or any other principle for that matter, if there is no symptom. Figure 8-3 Separated Modem Interface + recv() : char + hangup() Modem Implementation

Slide 57

Slide 57 text

Slide 58

Slide 58 text

Slide 59

Slide 59 text

ActiveRecord::Base

Slide 60

Slide 60 text

)PXPGUFOUIF QFSTJTUFODFTUSBUFHZ DIBOHFT

Slide 61

Slide 61 text

hand, the application is not changing i hange at differen times, then there is no uld smell of Needless Complexity. olary here. An axis of change is only an s not wise to apply the SRP, or any oth . Separated Modem Interface

Slide 62

Slide 62 text

%BUBWT 3FTQPOTJCJMJUZ

Slide 63

Slide 63 text

No content

Slide 64

Slide 64 text

r(SFHPSZ.PFDL *TTVF 3FTQPOTJCJMJUZDFOUSJD WTEBUBDFOUSJD EFTJHO https://practicingruby.com/articles/shared/bxstlrbnrjzt

Slide 65

Slide 65 text

%BUB DFOUSJD

Slide 66

Slide 66 text

.PEFMMJOH BSPVOE EBUB

Slide 67

Slide 67 text

3FBMXPSME FOUJUJFT

Slide 68

Slide 68 text

1FSTPO 0SEFS #MPH $PNQBOZ $PNNFOU 5BTL 1SPKFDU 1PTU

Slide 69

Slide 69 text

#FIBWJPVS BUUBDIFEUP &OUJUJFT

Slide 70

Slide 70 text

-PXDPIFTJPO

Slide 71

Slide 71 text

No content

Slide 72

Slide 72 text

No content

Slide 73

Slide 73 text

3FTQPOTJCJMJUZ DFOUSJD

Slide 74

Slide 74 text

.PEFMMJOH BSPVOE CFIBWJPVS

Slide 75

Slide 75 text

4OJQFS4UBUF%JTQMBZFS 0SEFS1SPDFTTPS 1PTU*OEFYFS 1SPKFDU%BUBCBTF.BQQFS "VDUJPO4OJQFS %PDVNFOU'JOEFS

Slide 76

Slide 76 text

%BUBJT KVTUEBUB

Slide 77

Slide 77 text

431JTFBTZ

Slide 78

Slide 78 text

"OBFNJD.PEFM

Slide 79

Slide 79 text

No content

Slide 80

Slide 80 text

/PU3BJMT TUZMF

Slide 81

Slide 81 text

%BUB 3FTQPOTJCJMJUZ 3FBMXPSMEFOUJUJFT 4PMVUJPOSFBMNBSUJGBDUT 3JDI.PEFM "OBFNJD.PEFM -PXDPIFTJPO 431 4MPXUFTUT 2VJDLUFTUT 3BJMT +&&

Slide 82

Slide 82 text

$FSFNPOZ WT&TTFODF

Slide 83

Slide 83 text

public!class!HelloWorld!{ !!!!public!static!void!main(String[]!args)!{ !!!!!!!!System.out.println("Hello,!World"); !!!!} } puts!'Hello,!World' WT

Slide 84

Slide 84 text

SECS_IN_ONE_DAY!=!24!*!60!*!60 Time.now!1!7!*!SECS_IN_ONE_DAY 7.days.ago WT

Slide 85

Slide 85 text

class!Catalog !!attr_accessor!:films,!:series !! !!def!initialize(films,!series) !!!!@films!!=!films !!!!@series!=!series !!end class!Catalog!

Slide 86

Slide 86 text

Publisher.new(post).publish post.publish WT

Slide 87

Slide 87 text

4UVBSU)BMMPXBZ &OEJOH-FHBDZ $PEF*O0VS -JGFUJNF http://thinkrelevance.com/blog/2008/04/01/ending-legacy-code-in-our-lifetime

Slide 88

Slide 88 text

'BJMTUPDBQUVSFJOUFOU 'BJMTUPDPNNVOJDBUFJOUFOU $BQUVSFTJSSFMFWBOUEFUBJM

Slide 89

Slide 89 text

&TTFODF*OUFOU

Slide 90

Slide 90 text

$FSFNPOZ*SSFMFWBOU%FUBJM

Slide 91

Slide 91 text

&⒎FDUJWFMZ DPNNVOJDBUJOH JOUFOU

Slide 92

Slide 92 text

4/3

Slide 93

Slide 93 text

'MFYJCJMJUZIBTB DPTUJOUFSNTPG $FSFNPOZ

Slide 94

Slide 94 text

5IFDPTUPG JOEJSFDUJPO

Slide 95

Slide 95 text

No content

Slide 96

Slide 96 text

s a d g h D c w f t i n a c t £È £x £{ £Î £Ó ££ £ä n Ç È x { Î Ó £ }ÓÊvÊÌiÊ ÕLiÀÊvÊ «iÌÃÊ *iÀÊÌi}À>Ìi`ÊÕVÌ 9i>À £x £Èä £È£ £ÈÓ £ÈÎ £È{ £Èx £ÈÈ £ÈÇ £Èn £È £Çä £Ç£ £ÇÓ £ÇÎ £Ç{ £Çx

Slide 97

Slide 97 text

No content

Slide 98

Slide 98 text

Psychological Review © by the American Psychological Association Vol. 101, No. 2, 343-352 For personal use only--not for distribution. The Magical Number Seven, Plus or Minus Two Some Limits on Our Capacity for Processing Information George A. Miller Harvard University This paper was first read as an Invited Address before the Eastern Psychological Association in Philadelphia on April 15, 1955. Preparation of the paper was supported by the Harvard Psycho-Acoustic Laboratory under Contract N5ori-76 between Harvard University and the Office of Naval Research, U.S. Navy (Project NR 142-201, Report PNR-174). Reproduction for any purpose of the U.S. Government is permitted. Received: May 4, 1955 My problem is that I have been persecuted by an integer. For seven years this number has followed me around, has intruded in my most private data, and has assaulted me from the pages of our most public journals. This number assumes a variety of disguises, being sometimes a little larger and sometimes a little smaller than usual, but never changing so much as to be unrecognizable. The persistence with which this number plagues me is far more than a random accident. There is, to quote a famous senator, a design behind it, some pattern governing its appearances. Either there really is something unusual about the number or else I am suffering from delusions of persecution.

Slide 99

Slide 99 text

Slide 100

Slide 100 text

your_brain.stack.length!>!7 =>!false

Slide 101

Slide 101 text

./app/models/concerns/availability.rb:89:in!`reference_program' ./app/models/concerns/availability.rb:87:in!`reference_program' ./app/models/scheduling.rb:220:in!`reference_program' ./app/models/rule.rb:171:in!`process_rule_schedulings!' ./app/models/rule.rb:170:in!`process_rule_schedulings!' ./app/models/rule.rb:60:in!`apply' ./app/controllers/rules_controller.rb:29:in!`update' ./app/models/user.rb:38:in!`with_current' ./app/controllers/application_controller.rb:70:in!`with_current_user' ./spec/acceptance/support/auth.rb:24:in!`call' ./lib/params_api_parser.rb:14:in!`call' ./spec/acceptance/support/webrat_compatibility.rb:164:in!`post' (eval):2:in!`send' (eval):2:in!`click_button' ./spec/acceptance/edit_vod_scheduling_rules_spec.rb:151 ./spec/acceptance/support/webrat_compatibility.rb:38:in!`call' ./spec/acceptance/support/webrat_compatibility.rb:38:in!`within' ./spec/acceptance/support/webrat_compatibility.rb:37:in!`within' ./spec/acceptance/edit_vod_scheduling_rules_spec.rb:148

Slide 102

Slide 102 text

FATAL: stack!level!too!deep

Slide 103

Slide 103 text

"CTUSBDUJPOIBTB DPTUJOUFSNTPG *OEJSFDUJPO

Slide 104

Slide 104 text

http://zedshaw.com/essays/indirection_is_not_abstraction.html

Slide 105

Slide 105 text

r;FE4IBX l"OVOCFMJFWBCMFMFWFMTPG JOEJSFDUJPOKVTUUPBEEB GVDLJOHPCKFDUUPBGVDLJOH DPMMFDUJPO5IJTJTUIFLJOEPG CVMMTIJUUIBUDIBQTNZBTT QVSQMFBOENBLFTNFXBOUUP FBUCBCJFTz http://zedshaw.com/essays/indirection_is_not_abstraction.html

Slide 106

Slide 106 text

3BJMTWT001

Slide 107

Slide 107 text

$POqJDUJOH USBEFP⒎T

Slide 108

Slide 108 text

3PPNGPS EFCBUF

Slide 109

Slide 109 text

3BJMT EFWJBUFT GSPNUIF00 EPHNB

Slide 110

Slide 110 text

*TUIBUPL PSOPU

Slide 111

Slide 111 text

Slide 112

Slide 112 text

l3BJMTNBLFTHPPE VTFSFYQFSJFODFJUT QSJNBSZHPBM XIFSF bVTFS`NFBOTUIFBQQ EFWFMPQFSz

Slide 113

Slide 113 text

69PWFS 001EPHNB

Slide 114

Slide 114 text

"UUIF CFHJOOJOH

Slide 115

Slide 115 text

BLB 5IF (PMEFO 1BUI 5IF 3BJMT 8BZ

Slide 116

Slide 116 text

)BNM 34QFD $VDVNCFS 1PTUHSF42- 1SFTFOUFST 4FSWJDFT $PODFSOT 3PMFT %$* .PDLT )FYBHPOBM %%% &3# 5FTU6OJU .Z42- $P⒎F4DSJQU

Slide 117

Slide 117 text

e(SBDJBT -VJTNJ$BWBMMÉ UXJUUFSDPNDBWBMMF HJUIVCDPNDBWBMMF QJOCPBSEJOVDBWBMMFUCJHNPEFMT