Write a lib today!

A talk about open sourcing and fun

Transcript

1. WRITE A LIB TODAY! PACO ESTEVEZ
2. WHY SHOULD I WRITE A LIBRARY?
3. LEARN CONCEPTS
4. EXPLORE FRAMEWORKS
5. ANTICIPATE YOUR OWN NEEDS
6. IMPROVE YOUR DOCUMENTATION SKILLS
7. EXPRESS IDEAS
8. GET CHALLENGED
9. TEST YOUR ORGANISATIONAL SKILLS
10. SOMETHING TO TALK WITH OTHER DEVELOPERS
11. HELP YOU FIND A NEW JOB
12. PRESENT AT EVENTS!
13. IT’S JUST FUN
14. WHY SHOULD MY COMPANY WRITE A LIB?
15. “IT DOESN’T GIVE US ANY COMPETITIVE ADVANTAGE”
16. “IT WILL HELP US ATTRACT TALENT”
17. “ENGINEERS FROM OTHER COMPANIES WILL HELP US”
18. “EVEN DISNEY HAS AN OPEN-SOURCE STRATEGY”
19. CHOOSE THE CORRECT LICENSE TO AVOID LIABILITY
20. MAKE THE LIBRARY A DERIVATIVE FROM THE INTERNAL CODE
21. RELEASE UNDER A SEPARATE ORGANISATION
22. PROVISION FOR MAINTENANCE
23. IT’S NOT LEGAL DEPT’S JOB SO MAKE IT WORTH THEIR WHILE
24. WHERE DO I PUBLISH IT?
25. GITHUB
26. HOW DO I SPREAD IT?
27. PUBLISHING A LIBRARY ▸ Is it going to last for the ages, have a community, and be referenced by other libraries? Maven Central or JCenter ▸ Is it a small helper, prototype, or proof of concept? Are you the only contributor? Does it have low maintenance? jitpack.io
28. WHERE DO I PROMOTE IT?
29. PROMOTING YOUR LIBRARY ▸ Android Arsenal ▸ Android Weekly ▸ /r/androiddev ▸ Slack groups ▸ Local android community ▸ Twitter
30. THE FEAR FIGHTING YOURSELF
31. YOU CAN RELEASE ANONYMOUSLY
32. HAVING A COMMUNITY IS OPT-IN
33. EVERYONE’S CODE SUCKED AT SOME POINT
34. EVERYTHING IS OLD IS NEW
35. INCOMPLETE LIBRARIES ARE OKAY TOO* *BUT ALWAYS ADD A README
36. LINKS pacoworks.com/ @fe_hudl github.com/pakoito tinyurl.com/LibDroidcon16 This presentation will be soon available on the droidcon London website at the following link: https://uk.droidcon.com/#skillscasts The Impostor Syndrome https://www.youtube.com/watch?v=eqhUHyVpAwE Android maven grade plugin https://github.com/dcendents/android-maven-gradle- plugin Jitpack https://jitpack.io/ Android Arsenal https://android-arsenal.com/ /r/androiddev https://reddit.com/r/androiddev API design http://www.apibook.com/blog/ Bob Ross - copyright © 1985–2016 by Bob Ross Inc Shenzhen IO - copyright © 2016 by Zachtronics