Years with PythonPyCon Korea 2017

iam@younggun.kim

1

x ,▶

2

• Do you use source control?

• Can you make a build in one step?

• Do you make daily builds?

• Do you have a bug database?

• Do you fix bugs before writing new code?

• Do you have an up-to-date schedule?

• Do you have a spec?

• Do programmers have quiet working conditions?

• Do you use the best tools money can buy?

• Do you have testers?

• Do you wanna build a snowman?

• Do new candidates write code during their interview?

• Do you do hallway usability testing?

Joel Test: https://www.joelonsoftware.com/2000/08/09/the-joel-test-12-steps-to-better-code/ 3

3/124

2017 ?• 2000 8 9 . 17 .• 2000 " PC" • ?

5

The joel test is still a pretty good test; there’s not much in there I would

change. — Joel Spolsky, March 2011

6

2011 2017• (footnote)

• .

• 3 ...

http://lmgtfy.com/?q=joel+test+for+2017 7

8

9

10

11

, Younggun Kim• http://younggun.kim

• Grants WG, Python Software Foundation

• former Director, Python Software Foundation

• former Organizer, PyCon Korea

• @scari_net

• " "

12

! ...?• ▶ ( )

• API

• C++

• PHP

• Python 2 <- !

13

14

• •

15

!Monolithic

16

!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

Microservices17

"Django"• • • .

https://www.slideshare.net/lqez/do-not-use-django-as-like-as-smartstudy 18

19

20

! !

oo !21

, !

22

23

24

NO

25

!

26

.. 3 ?

27

!28

29

*

30

31

32

Work it Harder Make it Better

Do it Faster Makes us Stronger

33

34

• • • • • • ,

35

• • • • . Blame •

36

• • •

37

Work AsynchrouslyIt's not faster*

but scales better

38

GitHub Activity

. .

39

40

...

-- ,

41

[ ] ? (2 )

1. ... ?2. .3. .4. ' ' .5. .

42