The document discusses the "Joel Test", a 12-question test from 2000 that evaluates whether a development team's practices are conducive to good software development. It notes the test is still relevant today with some minor changes. Some key practices it evaluates include source control usage, ability to do one-step builds, maintaining a bug database, prioritizing bug fixes over new features, and ensuring developers have quiet working conditions. The document also discusses trends in software architecture like monolithic vs microservices approaches.

1. Years with Python
PyCon Korea 2017
iam@younggun.kim
1

2. x ,
▶
2

3. • 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

4. 3/124

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

6. The joel test is still a pretty
good test; there’s not
much in there I would
change.
— Joel Spolsky, March 2011
6

7. 2011 2017
• (footnote)
• .
• 3 ...
http://lmgtfy.com/?q=joel+test+for+2017 7

8. 8

9. 9

10. 10

11. 11

12. , Younggun Kim
• http://younggun.kim
• Grants WG, Python Software Foundation
• former Director, Python Software Foundation
• former Organizer, PyCon Korea
• @scari_net
• " "
12

13. ! ...?
• ▶ ( )
• API
• C++
• PHP
• Python 2 <- !
13

14. 14

15. •
•
15

16. !Monolithic
16

17. !!!!!!!!!!!
!!!!!!!!!!!
!!!!!!!!!!!
Microservices
17

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

19. 19

20. 20

21. !
!
oo !
21

22. ,
!
22

23. 23

24. 24

25. NO
25

26. !
26

27. .. 3 ?
27

28. ! 28

29. 29

30. *
30

31. 31

32. 32

33. Work it Harder
Make it Better
Do it Faster
Makes us Stronger
33

34. 34

35. •
•
•
•
•
• ,
35

36. •
•
•
• . Blame
•
36

37. •
•
•
37

38. Work Asynchrously
It's not faster*
but scales better
38

39. GitHub Activity
. .
39

40. 40

41. ...
-- ,
41

42. [ ]
? (2 )
1. ... ?
2. .
3. .
4. ' ' .
5. .
42