How legacy projects are created?

A presentation at Let’s make software great again! meetup in November 2019 in Gdańsk, Poland by Paweł Lewtak

Slide 1

Slide 1

How legacy projects are created?

Slide 2

Slide 2

Paweł Lewtak TECH LEAD @ EG @pawel_lewtak

Slide 3

Slide 3

chaos

Slide 4

Slide 4

Slide 5

Slide 5

Slide 6

Slide 6

planning

Slide 7

Slide 7

coding without planning

Slide 8

Slide 8

WHAT first, HOW second

Slide 9

Slide 9

“it’s developer’s (mis)understanding, not expert knowledge that gets released to production” Alberto Brandolini

Slide 10

Slide 10

not what to BUILD - WHAT PROBLEM to solve

Slide 11

Slide 11

“Change is the only constant” Heraclitus

Slide 12

Slide 12

Slide 13

Slide 13

estimations are hard

Slide 14

Slide 14

Slide 15

Slide 15

estimation is not a deadline

Slide 16

Slide 16

estimation is like a model; perfect one doesn’t exist, good enough is useful

Slide 17

Slide 17

transparency

Slide 18

Slide 18

leader and responsibility

Slide 19

Slide 19

growth

Slide 20

Slide 20

let’s do Agile!

Slide 21

Slide 21

“Agile now means, we do half of scrum poorly and use Jira” Andy Hunt

Slide 22

Slide 22

code quality

Slide 23

Slide 23

Slide 24

Slide 24

it works for me so why write tests?

Slide 25

Slide 25

I don’t write tests due to lack of time

Slide 26

Slide 26

I don’t write tests due to lack of time I do write tests due to lack of time

Slide 27

Slide 27

documentation

Slide 28

Slide 28

what? how? who? where?

Slide 29

Slide 29

name of the service ## Point of contact and Slack channel ## Usage ## Running the service ## System ## Runbook ## Monitoring ## Documentation

Slide 30

Slide 30

not invented here

Slide 31

Slide 31

silos and rock stars

Slide 32

Slide 32

silos and rock stars

Slide 33

Slide 33

git

Slide 34

Slide 34

burnout

Slide 35

Slide 35

legacy?

Slide 36

Slide 36

legacy?

Slide 37

Slide 37

thank you

Slide 38

Slide 38

slides: noti.st/pawel-lewtak twitter.com/pawel_lewtak

Slide 39

Slide 39