Tweet
Tweet

Slide 1

Slide 1 text

Building a Culture Where Software Projects Get Done Greg Brockman CTO at Stripe @thegdb

Slide 2

Slide 2 text

No content

Slide 3

Slide 3 text

We don’t know how to build software

Slide 4

Slide 4 text

EXPECTED Disappointing Insane Today LIKELY Engineering timelines will slip

Slide 5

Slide 5 text

System complexity never decreases

Slide 6

Slide 6 text

Rewrites will always fail (that doesn’t stop people from trying, though)

Slide 7

Slide 7 text

You are not special

Slide 8

Slide 8 text

Choose wisely how you’re spending your time

Slide 9

Slide 9 text

Roll your own solution to your hardest problems, not your easiest ones

Slide 10

Slide 10 text

Balance creation versus maintenance

Slide 11

Slide 11 text

5.times {print “Automate”}

Slide 12

Slide 12 text

Once a bug is triggered, it will keep biting you on a short timeline, no matter how unlikely it seems

Slide 13

Slide 13 text

Invest in technology to support your rate of change

Slide 14

Slide 14 text

Tests aren’t for your benefit

Slide 15

Slide 15 text

Create a technology monoculture

Slide 16

Slide 16 text

You will have technical debt — and that’s good Image Credit: Philippe Kruchten

Slide 17

Slide 17 text

Pick a few standards

Slide 18

Slide 18 text

Have checks and balances against yourself

Slide 19

Slide 19 text

Minimize distance to the first production use Time to shard everything: 3 months (projected) ! Time to shard internal collection: 1 week

Slide 20

Slide 20 text

Have assumption questioners

Slide 21

Slide 21 text

Bus factor: not just for bus accidents

Slide 22

Slide 22 text

Use forcing functions (cautiously)

Slide 23

Slide 23 text

Have a good launch process in place

Slide 24

Slide 24 text

Have good post-hoc processes in place

Slide 25

Slide 25 text

Make collaboration great

Slide 26

Slide 26 text

Find communication sidechannels

Slide 27

Slide 27 text

Documentation should not be a primary source

Slide 28

Slide 28 text

Meetings: useful but costly

Slide 29

Slide 29 text

Have design dictators

Slide 30

Slide 30 text

Have lots of remotes or no remotes

Slide 31

Slide 31 text

Greg Brockman gdb@stripe.com @thegdb