Full Stack Community Talk

Speaking to people about community at the Full Stack meetup in Denver prior to Yehuda Katz interview.

Transcript

1. THE LONE DEVELOPER IS DEAD… COMMUNITY PREVAILS @JESSICAG
2. Stereotype: Lone Wolf Reality: Modern day software development is inherently community driven
3. Opensource API’s Gems Bundlers Compilers Databases —————————— Stackoverflow Slack Agile Stand-ups Retros
4. Food for thought…
5. If someone found out you were their team lead, would they be excited?
6. Would a new developer on your team be excited to know they are working with you?
7. Are people in your field aware of the problems you are solving?
8. Are you writing code in a vacuum? Would anyone coming up behind you know what the hell was going on?
9. Audience poll…
10. Who in this room uses open source software?
11. Besides GitHub, what do you use?
12. An easy assumption: Code is the only way to contribute to open source.
13. You can be a contributor without contributing code.
14. Open Source software has become common place, used by everyone.
15. 2nd course for thought…
16. Who paid for the compiler you used today?
17. Who paid for the database you used today?
18. Where the fuck did it come from?
19. OpenSource. It wasn’t so long ago that a compiler, a database were something we paid for. Now we share.
20. Where do I start?
21. Developer A: 3 years experience, involved in community Developer B: 5 years experience, isolated
22. You are as a good as the information and people you have access to
23. Community != being an extrovert
24. “But I hate talking to people… that’s why I’m a software engineer”
25. If you’re not the people person, you don’t have to go to meet ups and conferences all the time to be engaged.
26. Giving back can mean blog posts, helping with open source, mentoring, documentation.
27. Let’s look at the different circles of community
28. On your team: Discussion on problems, documentation, mentoring
29. In your company: Communicating and demonstration of problems you’ve solved, establishing culture to discuss problems, not isolating yourself.
30. In your local area: Mentoring, Speaking at local meetups, teaching weekend workshops, being engaged on Slack channels, helping out.
31. In your space: Mentoring, speaking at conferences, contributing to open source projects, creating API’s, writing blog posts — once you solve a simple problem, give back and tell people about it!
32. Giving back 10x before asking 1x
33. Story Time
34. Sandi Metz created POODR (Practical Object-Oriented Design in Ruby) because she had consumed a lot of open source data and wanted to give back
35. What can we gleam from this? Our community is better with all of us giving back and engaging with one another. We are stronger for it and better solutions and software come of it.
36. Large open source projects, are a result of a community coming together and building something awesome.
37. RIP Lone Wolf git commit -am ‘hello world !’
38. THANK YOU FOR YOUR TIME! @JESSICAG