1.
HOW TO KEEP CALM
AND SHIP IT

2.
hello
my name is
@JUOKAZ

3.
IF SOMETHING BIG HAPPENS,
HOW QUICKLY CANYOU
REACT?

4.
MVP

5.
WHY DOESTHIS MATTER?

6.
ANY DAY NOT IN
PRODUCTION IS LOST
POTENTIAL

7.
HOWTO GO FROM AN IDEA
TO IMPLEMENTATION IN DAYS

8.
MOVE FAST AND BREAK THINGS
- Mark Zuckerberg, Facebook

9.
REQUIREMENTS

10.
UNCLEAR ORIGINAL
SPECIFICATIONS

11.
CYCLES OF CHANGES AND
TESTING

12.
LACK OF UNDERSTANDING
WHY KILLS PROJECTS

13.
“YOU SHOULD ADD A
BUTTON/CHECKBOX”

14.
IMPACT MAPPING
http://www.impactmapping.org/

15.
1. why are we doing this
2. who is affected by this
3. how should the behavior change
4. what can we do as an organization

16.
ALWAYS HAVE A PLAN

17.
IDENTIFY WHATYOU
CANNOT BREAK

18.
FEATURE-CREEP KILLS
PROJECTS

19.
AGILE?

20.
IF IT'S HARD, CUT SCOPE
- Wiggins' Law

21.
PROTOTYPING

22.
FAMILIARTOOLSET

23.
TOOLBOX
• Bootstrap for all frontend work
• Web framework of choice
• Database of choice
• ect.

24.
FLASK-SKELETON
https://github.com/juokaz/flask-skeleton

25.
BUILD DELIVERABLE
PRODUCTS

26.
EVERY SUB-FEATURE SHOULD
WORK

27.
“WE CAN ALWAYS FIX IT
LATER”

28.
PRETTY APPS > WORKING APPS

29.
FAKE/HACK IRRELEVANT PARTS

30.
CONTINUOUS DELIVERY

31.
12-FACTOR APP
http://12factor.net/

32.
1. Codebase - One codebase tracked in revision control
2. Dependencies - Explicitly declare and isolate
dependencies
3. Config - Store config in the environment
4. Backing Services -Treat backing services as attached
resources
5. Build, release, run - Strictly separate build and run
stages
6. Processes - Execute the app as one or more stateless
processes
7. Port binding - Export services via port binding
8. Concurrency - Scale out via the process model
9. Disposability - Maximize robustness with fast
startup and graceful shutdown
10. Dev/prod parity - Keep development, staging,
and production as similar as possible
11. Logs -Treat logs as event streams
12. Admin processes - Run admin/management
tasks as one-off processes
12-FACTOR APP

33.
TDD?

34.
VERIFICATION

35.
DOCKER
http://docker.com/

36.
CHECKLIST
• Push to master
• Build a Docker container containing the app
• Runs tests, code formatting checks, database
migrations validation
• If all is ok, the Docker container is a stable build
• Then deploy to staging and/or production

37.
FEEDBACK LOOP

38.
DEVELOPERS ROLE
• Owners of a project/feature/system
• Responsible for fixing if it’s broken
• Slack operations room

39.
METRICS

40.
STATSD/GRAPHITE
https://github.com/etsy/statsd

41.
“NO ONE NOTICES A WEBSITE
BROKEN FOR 2 MINUTES”

42.
USERS

43.
IN SHORT
• Collect requirements and make aTODO list even
for small projects
• Prototype using familiar tools and frameworks
• Continuos delivery
• Feedback loop

44.
THANKS!
Juozas Kaziukėnas
@juokaz