My 10 steps to tech community contributions

Slide 1

Slide 1 text

My 10 steps to tech community contributions By Lars Gyrup Brink Nielsen

Slide 2

Slide 2 text

1. Internal knowledgesharing

Slide 3

Slide 3 text

Written internal knowledge sharing • Shared libraries and tooling • Onboarding • System and project architecture • Recipes • Inspiration

Slide 4

Slide 4 text

Person-to-person internal knowledgesharing • Hackathons • Internal tech talks and workshops • Mentoring • Pair programming • Code review

Slide 5

Slide 5 text

2. Speaking at meetups

Slide 6

Slide 6 text

Tips for speaking at meetups • Practice, practice, practice. • Remove unnecessary content. • Speak the words out loud when rehearsing. • Engage with your audience. • Don’t feel bad. It feels a lot worse than it is 🙂

Slide 7

Slide 7 text

3. Writing tech articles

Slide 8

Slide 8 text

Tips for writing tech articles • Write in a natural language voice. • Focus on one core topic per article. • Avoid abbreviations for a world-wide audience. • Find your niche. • Get a mentor. • Stop listing code as images in articles.

Slide 9

Slide 9 text

My 3 main ingredients for tech writing • Explain the theory and concepts on an abstract level. • Use simple, but realistic code examples. • Visualize the concepts.

Slide 10

Slide 10 text

4. Contributing to open source software

Slide 11

Slide 11 text

Tips for contributing to open source software • Documentation contributions is a great place to start. • Focus on a few projects. • Don’t waste your time on complicated development environments.

Slide 12

Slide 12 text

5. Speaking at conferences

Slide 13

Slide 13 text

Speaking at conferences

Slide 14

Slide 14 text

Speaking at conferences

Slide 15

Slide 15 text

Tips for speaking at conferences • Time your rehearsals. • Export your slideshow as a PDF. • Store your presentation on a USB stick. • Visit the speakers room and speakers events.

Slide 16

Slide 16 text

6. Mentoring and editing tech writers

Slide 17

Slide 17 text

Pro tips for writing tech articles • No fluff! Add value, not volume. • Get straight to the point. • Make longer articles easy to scan. • Consider splitting longreads into individual articles to make them easier to finish and reference. • Include your own perspective and experience to add unique value. • Finish strong.

Slide 18

Slide 18 text

7. Receiving the Microsoft MVP Award

Slide 19

Slide 19 text

The Microsoft MVP Award process 1. Make community contributions. 2. Get nominated by a Microsoft MVP or Microsoft employee. 3. Submit your community contributions. 4. You are compared to MVPs and nominees from the same region and product category. 5. Receive the Microsoft MVP Award. 6. Your contributions are reset at July 1st. 7. Go to 1, but skip 2.

Slide 20

Slide 20 text

8. Authoring a book

Slide 21

Slide 21 text

Tips for authoring a book • It takes a lot of time. • Publishers can take care of review, design, distribution, marketing, and more. • Publishers want a detailed outline and an estimated schedule. • Don’t do it to get rich. • It takes a lot of time.

Slide 22

Slide 22 text

9. Maintaining open source software

Slide 23

Slide 23 text

Tips for maintaning open source software • Find a project that you like or start your own. • Find a team that you like. • Write documentation. • Encourage and support contributions and feedback. • There’s a difference between open source software and openness in software.

Slide 24

Slide 24 text

Openness in software projects https://www.linuxfoundation.org/en/resources/publica tions/determining-the-true-openness-of-open-source- projects/