OSCON - Haunt

Introduction of Haunt at oscon

Transcript

1. @fat Jul 2012 OSCON Thursday, July 19, 12
2. I’m @fat Thursday, July 19, 12
3. I work at twitter Thursday, July 19, 12
4. I write libraries Thursday, July 19, 12
5. Bootstrap, Ender, Hogan.js Thursday, July 19, 12
6. MooTools-flot, Stache, snapysnap Thursday, July 19, 12
7. Sometimes when I’m feeling saucy I open pull requests Thursday, July 19, 12
8. These are largely rejected or backed out after a merge Thursday, July 19, 12
9. I’ve been #1 on hacker news twice Thursday, July 19, 12
10. Thursday, July 19, 12
11. This is my real avatar on the internet Thursday, July 19, 12
12. People always think I’m high when I give these presentations Thursday, July 19, 12
13. People always think I’m High when i give these presentations Thursday, July 19, 12
14. Don’t tweet that, it hurts my feelingz Thursday, July 19, 12
15. I say “like” a lot Thursday, July 19, 12
16. I curse Thursday, July 19, 12
17. The only thing which consistently impresses me is 4chan Thursday, July 19, 12
18. I live in the tenderloin Thursday, July 19, 12
19. I have a .xxx domain Thursday, July 19, 12
20. And perhaps worst of all I read books Thursday, July 19, 12
21. And not particularly good ones Thursday, July 19, 12
22. One of the authors I read a fair amount of is Karel Čapek Thursday, July 19, 12
23. Thursday, July 19, 12
24. ČČapek wrote a number of works on brutal fascist dictatorships Thursday, July 19, 12
25. But he’s most famous for a sci-fi play he wrote in 1920 R.U.R. Thursday, July 19, 12
26. A dystopian work about a factory populated with androids Thursday, July 19, 12
27. Thursday, July 19, 12
28. It start’s with a story about a man named Rossum Thursday, July 19, 12
29. Who accidentally discovers a chemical similar to protoplasm Thursday, July 19, 12
30. Rossum attempts to make a real dog and man, but fails Thursday, July 19, 12
31. Old Rossum was trying to prove God not just useless, but absent Thursday, July 19, 12
32. Nephew comes to visit uncle and argues with old uncle Rossum Thursday, July 19, 12
33. Young Rossum just trying to… Thursday, July 19, 12
34. Eventually, Young Rossum locks his uncle in a laboratory Thursday, July 19, 12
35. And uses the formula to build robots Thursday, July 19, 12
36. Soon he’s building factories and robots by the thousands Thursday, July 19, 12
37. By the 1950s, you can get robots on the cheap Thursday, July 19, 12
38. The economy is amazing and so is the quality of life Thursday, July 19, 12
39. Then this girl Helena shows up Thursday, July 19, 12
40. Thursday, July 19, 12
41. what if computers don't like being programmed prince M I L Ǝ S @iano 25 JUN Thursday, July 19, 12
42. maybe computers just want to chill and play screen savers all day prince M I L Ǝ S @iano 25 JUN Thursday, July 19, 12
43. Then there’s a robot revolt and it turns into a whole thing Thursday, July 19, 12
44. But what about dat quality of life thing? Thursday, July 19, 12
45. A few months ago I was at Thursday, July 19, 12
46. Between sessions I was talking to TJ Holowaychuk Thursday, July 19, 12
47. We bonded over having panic attacks about github notifications Thursday, July 19, 12
48. Thursday, July 19, 12
49. Turns out, this is a pretty common problem Thursday, July 19, 12
50. It’s a good problem Thursday, July 19, 12
51. But still a problem Thursday, July 19, 12
52. What makes it worse is github doesn’t offer maintainers much help Thursday, July 19, 12
53. Out of desperation you begin to see things like… Thursday, July 19, 12
54. Thursday, July 19, 12
55. Thursday, July 19, 12
56. But I still found myself spending 3-5 hours a week on issues alone Thursday, July 19, 12
57. What’s worse, most of these issues aren’t issues with the library Thursday, July 19, 12
58. They are support questions, duplicates, incomplete reports, etc. Thursday, July 19, 12
59. This becomes both exhausting and incredibly discouraging Thursday, July 19, 12
60. What’s worse, we get so overrun that we forget to innovate Thursday, July 19, 12
61. I can close 50+ issues without committing a single line of code ಠ_ಠ Thursday, July 19, 12
62. I’ve seen a few solutions to this problem Thursday, July 19, 12
63. Some projects add contributors who only manage tickets Thursday, July 19, 12
64. But it’s hard to find people, let alone the right people Thursday, July 19, 12
65. Some projects begin moving ticketing off network Thursday, July 19, 12
66. But this means inconsistent ticket locations and implementations Thursday, July 19, 12
67. Instead, what if we could just clone ourselves? Thursday, July 19, 12
68. This of course is the Old Rossum approach Thursday, July 19, 12
69. But wut if we focused on really simple tasks a la Young Rossum? Thursday, July 19, 12
70. The evening after I wrote some docs for a new service Thursday, July 19, 12
71. A bot which would implement Necolas’s issue-guidelines Thursday, July 19, 12
72. But it shaped up to be a huge undertaking with limited value Thursday, July 19, 12
73. Which is to say, value for Nicolas and I, but no one else Thursday, July 19, 12
74. About a month later Thursday, July 19, 12
75. how did your github bot thing go? TJ Holowaychuk @TJHolowaychuk 1:10 AM Thursday, July 19, 12
76. Translation Can i use ur robot pls? Thursday, July 19, 12
77. @tjholowaychuk sadly haven't had time to finish it yet :( I added @sayer to the project but we've both been pretty busy ♒∆✝ @fat 1:11 AM Thursday, July 19, 12
78. Translation I abandoned it, but blame @sayrer Thursday, July 19, 12
79. haha ok cool, I could definitely use something like that these repo issues are getting out of control TJ Holowaychuk @TJHolowaychuk 1:15 AM Thursday, July 19, 12
80. Translation FML. ok. I’ll write my own. Thursday, July 19, 12
81. bahaha my bot backfired on me and started closing the wrong shit, definitely needs a dry- run mode TJ Holowaychuk @TJHolowaychuk 2:26 AM Thursday, July 19, 12
82. Translation fuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuu Thursday, July 19, 12
83. Naturally, I first lol’d at all the wrongly closed issues Thursday, July 19, 12
84. Then got obsessively interested in actually building this thing Thursday, July 19, 12
85. But with a new, goal: I wanted it to be “Universal” Thursday, July 19, 12
86. To begin I started researching bots Thursday, July 19, 12
87. Chatterbots, spambots, botnets, gaming bots, votebots, etc. Thursday, July 19, 12
88. I found Bots are just apps that run automated tasks over the web Thursday, July 19, 12
89. But I wanted something slightly different Thursday, July 19, 12
90. An app that ran automated tests over the web Thursday, July 19, 12
91. I was hoping this would offer more flexibilty and be easier to evolve Thursday, July 19, 12
92. So for the past two months, i’ve been working on just that Thursday, July 19, 12
93. And today I’m happy to be open sourcing it Thursday, July 19, 12
94. Haunt something similar to Rossum’s protoplasm Thursday, July 19, 12
95. Which is to say, a node module for creating robots || services Thursday, July 19, 12
96. Haunt allows you to run unit tests against issues and pull-requests Thursday, July 19, 12
97. Then make decisions about closing, tagging, and commenting Thursday, July 19, 12
98. All programmatically Thursday, July 19, 12
99. For bootstrap I wrote the following simple assertions Thursday, July 19, 12
100. Pull-Requests should always be made against -wip branches Thursday, July 19, 12
101. Pull-Requests should always be made from feature branches Thursday, July 19, 12
102. Pull-Requests should always include a unit test if changing js files Thursday, July 19, 12
103. Issues should include a jsfiddle/jsbin if tagged as JS Thursday, July 19, 12
104. These 4 tests invalidate 37 of 42 pull requests and 63 of 88 issues Thursday, July 19, 12
105. Issues which I would have had to manually comment and close Thursday, July 19, 12
106. But it doesn’t stop there Thursday, July 19, 12
107. You could write more complex assertions to check for duplicates Thursday, July 19, 12
108. Or already resolved issues in your code Thursday, July 19, 12
109. You could even use it to run your actual test suite Thursday, July 19, 12
110. Or use it to run a linter like jshint Thursday, July 19, 12
111. Or simple things like tagging all issues with >10 +1’s as “popular” Thursday, July 19, 12
112. Because this is just JS the potential is limitless Thursday, July 19, 12
113. So just checkout http://git.io/haunt to find out how it works Thursday, July 19, 12
114. thx and follow @fakeangus <3 Thursday, July 19, 12