Slide 1

Slide 1 text

MAKE frameworks not hostages @helmedeiros

Slide 2

Slide 2 text

Erich Gamma Design Patterns: Elements of Reusable Object-Oriented Software

Slide 3

Slide 3 text

they want to do too much for you FRAMEWORKITIS 10 years ago

Slide 4

Slide 4 text

FRAMEWORK reduce your need to resolve solved problems What is that for?

Slide 5

Slide 5 text

how it works, who adapts to whom, how it is production ready, it evolved and you FRAMEWORK Depends? When?

Slide 6

Slide 6 text

how well is it coded? is it cohesive? Are their responsibilities unique? Is it working with Inversion of Control? FRAMEWORK Patterns? SOLID?

Slide 7

Slide 7 text

COMMUNITY Collaborative? Help others learn? Java, JavaScript, Ruby, Python, etc.. Is Communities’ maturity influences on the quality of frameworks created?

Slide 8

Slide 8 text

were effective 10 years and  all  effor*s It seems that

Slide 9

Slide 9 text

to be the case REALLY?!?! it  doesn’t  seem Hummmm

Slide 10

Slide 10 text

NEW CHALLENGES COMPUTATIONAL AND MANY PEOPLE TO SOLVE THEM

Slide 11

Slide 11 text

No content

Slide 12

Slide 12 text

NOT ALWAYS… we have time to see how a problem was explored and solved

Slide 13

Slide 13 text

No content

Slide 14

Slide 14 text

NOT ALWAYS… We find time to subtract differences add up efforts and multiply the results

Slide 15

Slide 15 text

2013 2104 2105 NOT ALWAYS… We have time to follow, adapt and contribute to all the madness that is out there

Slide 16

Slide 16 text

WHEN YOU USE take care

Slide 17

Slide 17 text

what would you like to happen, not how Declarative vs Imperative Take care…

Slide 18

Slide 18 text

No content

Slide 19

Slide 19 text

No content

Slide 20

Slide 20 text

there isn’t a single solution to every problem ... full-stack framework? MODULAR to monolithic Take care…

Slide 21

Slide 21 text

phalcon Symphony doctrine + Laravel vs Slim

Slide 22

Slide 22 text

VUE.JS REACTIVE BREEZE KNOCKOUT REACT vs

Slide 23

Slide 23 text

No content

Slide 24

Slide 24 text

know why that was created and how it will evolve Intentions vs uses Take care…

Slide 25

Slide 25 text

No content

Slide 26

Slide 26 text

when you create take care

Slide 27

Slide 27 text

balance the desire to innovate with stability preserve stability over time Take care…

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

anyone knows and has an interest beyond the core? BEYOND THE CORE LIB Take care…

Slide 32

Slide 32 text

No content

Slide 33

Slide 33 text

No content

Slide 34

Slide 34 text

understand it with one look CODE SIMPLICITY Take care…

Slide 35

Slide 35 text

No content

Slide 36

Slide 36 text

No content

Slide 37

Slide 37 text

ANY CURE? is there

Slide 38

Slide 38 text

still exists and is cyclically renewed FRAMEWORKITIS 10 year after

Slide 39

Slide 39 text

No content

Slide 40

Slide 40 text

abstraction is good but take it easy frameworkS ARE NOT LANGUAGES is there a cure?

Slide 41

Slide 41 text

now favor small, simple, solid libraries that I can understand and use easily, can be easily replaced? FAVOR toolkits OR libraries is there a cure?

Slide 42

Slide 42 text

stay tuned and try hard before going to production remain skeptical is there a cure?

Slide 43

Slide 43 text

analyse your problem and take it easy and if all else fails is there a cure?

Slide 44

Slide 44 text

a big price COMES WITH a  price All magic

Slide 45

Slide 45 text

Thanks! @helmedeiros