Daniel Hengeveld's talk from Future Insights Live 2014 in Las Vegas: "When we work on software with others, we expect that our collaborators will share their *code* in a way that makes it easy to see what they’ve been working on. We should have the same expectation for all the *other* artifacts of software development." Miss his talk? Join us at a future show: www.futureofwebapps.com. Sign up for our newsletter at futureinsights.com and get 15% off your next conference.

1. DEVELOPING
IN PUBLIC

3. STORY TIME

6. ▸ navigation team couldn't drive
▸ system engineering checks were weak
▸ informal communication channels

7. some communications channels among project
engineering groups were too informal

8. too informal

10. NOT A SOFTWARE
PROBLEM?

11. A HUMAN PROBLEM

12. HOW CAN WE DO
BETTER?

13. SOFTWARE
ARCHAEOLOGY

14. commit 9e3ce0965868f1e9af385951cf1e22960d0edf0d
Author: Kevin Sawicki & Nathan Sobo <kevin+nathan@github.com>
Date: Wed May 21 18:04:44 2014 -0600
Add thruster input
We need to take the thrust input from the propulsion bus and fire the thrusters
accordingly

15. OK, maybe we've mostly solved this for code.

16. ▸ Use version control
▸ write good commit messages
▸ use feature branches
▸ the list goes on...

17. I GUESS MY TALK CAN
BE OVER?

18. /NOPE

19. HERE'S A CLICHÉ

20. It's better to work together
than to work alone

22. What if “together” is miles and hours apart?

23. What did she do yesterday?

24. What did I do yesterday?"

25. SOFTWARE
!=
SOFTWARE DEVELOPMENT

26. SOFTWARE
⊆
SOFTWARE DEVELOPMENT

27. [********] Coding
[***] Communicating / coordinating
[**] Reviewing code / PRs to merge
[**] Runtime / CI / infrastructure
[*] Long term project planning

29. SO

30. WHAT'S THE WORK?

31. (Here come some dirty words)

33. MANAGEMENT

35. POLITICS

36. Other people are your allies, in other words, but that
alliance takes sustained effort to build. And you should
be prepared for that, not irritated by it.
Ed Catmull

38. DOCUMENTATION

40. TRANSCRIPTION

42. STARING OFF INTO
SPACE DESIGN

43. Oh, and just one more thing...

45. CODING

46. SOME TOOLS

47. WIP PRS

48. ALWAYS BE PAIRING

49. CHATOPS

50. /ci status <repo>/<branch>
/deploy team to stg
/graph me -10min @app-perf (or something)
/procs unicorn
/resque critical
/conns fe1
/who's on call

51. WHY IS THIS STUPID
CHAT BOT SO
IMPORTANT?

52. What if we don't have a Hubot?

53. A SELF-REPORTING
CULTURE

54. EMBRACE GOOD TOOLS

55. YOUR TOOLS
=
YOUR OFFICE

56. BE PREDICTABLE

57. prefer communication

58. DON'T BLOCK

59. TELL ME WHY

60. TRULY PRODUCTIVE
REMOTE WORK

61. FAST ONBOARDING

62. TRANSPARENT
STRATEGIES
&
#REALTALK

63. NO ONE GETS LOST

64. DEVELOP IN PUBLIC BECAUSE..
▸ it enables remote work
▸ gets new people started fast
▸ teaches your teammates how your brain works
▸ Exposes failure early enough to fix it

65. Daniel Hengeveld
Softwaresman, GitHub
@thedaniel
thedaniel.github.io