Sharing, modules, and Unix

The story of our development culture.

Transcript

1. A story of sharing, modules, and Unix Bartek Ciszkowski @bartekci
2. G Adventures Software Department
3. We wanted.. • To have transparency • Be contributors to the open source community • Build and use pluggable modules
7. This helped, but we still looked like this.
8. We began taking on projects that crossed teams.
9. • mkdir gapi-layer; • mkdir pouch; • mkdir gapi-web; G API
10. Cross-Pollination Began
11. Project was more accessible
12. Wrote docs.
13. Hmm…
14. Next, we wanted to add Webhooks to our API
15. mkdir gapi-layer/ webhooks?
16. Hold on!
    ! mkdir captainhook;
17. G Adventures API Webhooks Dispatcher is born.
18. • Exposed a simple HTTP interface for systems to interact • It does its sole job, and does it well • Other systems don’t care about its implementation
19. Wrote focused docs.
20. Testing became accessible
22. Credit substack.net
23. Write programs that do one thing and do it well. Write programs to work together.
24. We started thinking how we could better design our code.
25. “TinCan is a communications tool built as a pluggable Django application”
26. “lexi-complete is a data agnostic dictionary auto-complete tool for your JS app.”
27. “GeoData is a pluggable Django application to model and load common geographic meta-info.”
28. We began building modular applications with a focus on sharing
29. How we look now
30. 4 Open Source Projects with documentation & tests
31. Accessible Code Provides More Business Insight
32. Writing words > 4000 words of focused documentation in past year
33. Still learning • Sharing developers across teams. • Better documentation standards when we open source. Versioning, i18n • Silos still exist. Tough as meteorite
34. • Write applications that are simple and clear • Allow for any developer to easily jump in • Focused documentation • Accessible tests
35. When in doubt, think of Unix
36. Thank You!
37. developers.gadventures.com