[图解]软件开发团队的脓包-02-口号党的危害

0
00:00:00,130 --> 00:00:03,710
今天我们来说一下开发团队的第二个脓包

1
00:00:04,530 --> 00:00:05,480
口号党

2
00:00:10,100 --> 00:00:12,980
口号党就是说，他只会喊口号

3
00:00:12,980 --> 00:00:15,620
但是没有提供相应的方法

4
00:00:15,620 --> 00:00:16,820
比如说，他喊

5
00:00:17,130 --> 00:00:18,726
我们只做最重要的需求

6
00:00:18,726 --> 00:00:20,500
这个产品经理喊的

7
00:00:22,050 --> 00:00:22,971
问题就来了

8
00:00:22,971 --> 00:00:24,630
你怎么知道哪个最重要

9
00:00:25,070 --> 00:00:26,150
拍脑袋？

10
00:00:27,060 --> 00:00:28,340
没有方法

11
00:00:28,630 --> 00:00:30,020
或者架构师喊

12
00:00:30,800 --> 00:00:32,680
设计要分离变和不变

13
00:00:33,220 --> 00:00:34,351
太有道理了

14
00:00:34,351 --> 00:00:35,030
问题是

15
00:00:36,470 --> 00:00:38,607
你怎么知道哪些变哪些不变

16
00:00:38,607 --> 00:00:39,320
你抓阄啊？

17
00:00:41,220 --> 00:00:43,700
或者喊，领域驱动设计

18
00:00:44,480 --> 00:00:44,797

19
00:00:44,797 --> 00:00:45,431
对呀

20
00:00:45,431 --> 00:00:47,650
领域驱动，好啊

21
00:00:47,990 --> 00:00:48,185

22
00:00:48,185 --> 00:00:49,360
那请问

23
00:00:49,360 --> 00:00:50,340
领域怎么驱动

24
00:00:51,460 --> 00:00:52,720
没有方法

25
00:00:56,010 --> 00:00:59,300
那我们知道，做事情有三个境界

26
00:00:59,920 --> 00:01:00,588
有口号有方法

27
00:01:00,588 --> 00:01:02,370
可以这样分

28
00:01:02,370 --> 00:01:03,706
有口号有方法

29
00:01:03,706 --> 00:01:06,380
没口号没方法，有口号没方法

30
00:01:07,030 --> 00:01:08,764
第一个当然最好了

31
00:01:08,764 --> 00:01:09,150
对吧

32
00:01:09,430 --> 00:01:10,770
那后面这两个

33
00:01:11,160 --> 00:01:13,190
大家觉得哪个最糟糕

34
00:01:14,990 --> 00:01:15,202
哎

35
00:01:15,202 --> 00:01:17,747
实际上第三个最糟糕

36
00:01:17,747 --> 00:01:18,383
有口号没方法

37
00:01:18,383 --> 00:01:19,020
最糟糕

38
00:01:21,070 --> 00:01:22,060
为什么

39
00:01:24,360 --> 00:01:25,290
因为

40
00:01:26,370 --> 00:01:28,050
口号这个东西

41
00:01:28,490 --> 00:01:29,590
很容易喊

42
00:01:31,190 --> 00:01:32,890
但是他喊了之后

43
00:01:33,430 --> 00:01:35,330
带来第一个危害就是

44
00:01:36,680 --> 00:01:38,520
无意识的自我陶醉

45
00:01:38,520 --> 00:01:41,050
他就把这个口号当成什么

46
00:01:41,330 --> 00:01:42,470
当成方法了

47
00:01:42,470 --> 00:01:43,610
当成一切了

48
00:01:43,890 --> 00:01:44,515
他喊完

49
00:01:44,515 --> 00:01:46,599
我们只要做最重要的需求

50
00:01:46,599 --> 00:01:46,807

51
00:01:46,807 --> 00:01:48,892
要分离变和不变之类的

52
00:01:48,892 --> 00:01:51,810
或者说，我们要敏捷什么之类的

53
00:01:53,010 --> 00:01:53,930
然后

54
00:01:54,210 --> 00:01:56,036
他就满足了，就陶醉了

55
00:01:56,036 --> 00:01:57,863
觉得，哇，我太厉害了

56
00:01:57,863 --> 00:02:01,060
这么厉害的道理我都知道

57
00:02:01,340 --> 00:02:02,200
太牛了

58
00:02:02,480 --> 00:02:04,070
其他都小意思了

59
00:02:05,260 --> 00:02:05,867
然后呢

60
00:02:05,867 --> 00:02:08,500
他也不认真去思考怎么做到了

61
00:02:09,940 --> 00:02:13,750
甚至什么，连以前自己做得好的一些

62
00:02:15,370 --> 00:02:17,690
做法，虽然不是很完美

63
00:02:18,100 --> 00:02:18,970
但是呢

64
00:02:19,970 --> 00:02:21,270
他做熟了的

65
00:02:21,640 --> 00:02:22,820
甚至他都

66
00:02:23,190 --> 00:02:24,570
不继续去做了

67
00:02:24,850 --> 00:02:26,550
因为他觉得有口号就够了

68
00:02:30,220 --> 00:02:31,940
无意识的自我陶醉

69
00:02:32,690 --> 00:02:34,570
那第二个危害就是

70
00:02:34,850 --> 00:02:36,670
有意识的胡作非为了

71
00:02:39,060 --> 00:02:39,990
他在

72
00:02:40,270 --> 00:02:41,833
口号的掩护之下

73
00:02:41,833 --> 00:02:44,290
他在开发团队里面就瞎搞

74
00:02:45,450 --> 00:02:47,700
当你去纠正他的时候

75
00:02:48,370 --> 00:02:49,814
他就问你一句

76
00:02:49,814 --> 00:02:51,740
难道你不想什么吗

77
00:02:52,580 --> 00:02:53,150

78
00:02:54,910 --> 00:02:57,560
你都不好去反驳他

79
00:02:59,230 --> 00:03:00,200
比如说

80
00:03:01,910 --> 00:03:03,470
他说，我们要敏捷

81
00:03:03,750 --> 00:03:04,450
对吧

82
00:03:05,320 --> 00:03:06,540
然后就瞎搞

83
00:03:07,340 --> 00:03:09,969
你要去阻拦他，他就问你一句

84
00:03:09,969 --> 00:03:12,360
难道你不想变得敏捷吗

85
00:03:13,840 --> 00:03:14,980
你还怎么说

86
00:03:15,830 --> 00:03:17,140
这没法说了

87
00:03:17,420 --> 00:03:18,270
对不对

88
00:03:18,610 --> 00:03:20,950
所以呢，他就在这个掩盖之下

89
00:03:22,250 --> 00:03:23,076
胡作非为

90
00:03:23,076 --> 00:03:25,347
而且出了问题还不好追究

91
00:03:25,347 --> 00:03:26,380
毕竟怎么样

92
00:03:26,920 --> 00:03:28,900
初衷是好的嘛！

93
00:03:28,900 --> 00:03:29,890