Writing in the front

Almost all technical teams are sharing technology, and sometimes it is not good enough to organize sharing and always want to do better. This paper summarizes the process of our team’s technology sharing to help the team improve the quality of technology sharing. If you have better suggestions, please leave a message.

Why do technology sharing

The benefits of technology sharing are many, and here are just a few;

  1. Expand the field of knowledge, can have a wider knowledge reserve
  2. Learn new things quickly
  3. Make the original knowledge more solid
  4. Improve the knowledge system
  5. Give the players a chance to show themselves
  6. Set up a learning technology team to make the company more competitive
  7. Leave a text or video profile and get a raise when you change jobs. In this era of paying for knowledge, persistence can be lucrative
  8. Increase your influence and raise your salary

Sometimes shy programmers are reluctant to share because they don’t feel confident. This requires the TL’s help and the encouragement of the players to help them grow.

Pain points

Technology sharing has common pain points

  1. Not sure what to share
  2. The audience is better than I am
  3. How do YOU prepare to share

These pain points can be especially frustrating for new teams and programmers. Below is a summary of our IT sharing experience in terms of how to organize and how to prepare a share.

“The audience is better than ME” is a false statement. If the presenter is well prepared, he or she knows at least 90% more about the subject than the audience. If the stage has 1-2 big guy, can help share person correct, perfect also is very good. In any case, the most benefit or share the person himself!

How to Organize sharing

PS: First of all, there needs to be a TL for continuous learning. If the team’s tech-leaders stop learning, IT sharing will definitely fail. Thanks to boss Jim for leading us step by step to improve our technology.

How to choice

TL organizes team members to brainstorm, list and categorize the technologies they want to learn, and divide them into particles that can be shared once. Such as

Front end:


— reactjs + redux


— vuejs + vuex + vue-router

In fact, ReactJS itself is not difficult, the actual combat needs to understand Redux, Hoc, etc. So in 40 minutes or so of sharing, just sharing the React syntax is obviously boring. For the choice and scope of the topic, it is necessary to determine in advance, to ensure that 40 minutes of work. Sharing is not teaching. There is no need to hand over all the details to each participant.

Organizational process

After deciding on the topic of sharing, you need to arrange sharing and host. The host is responsible for booking the conference room, following up the sharing to make sure that the sharing can proceed as planned, receiving the PPT of the sharing and the preview materials of the audience, distributing them to the participants, and informing all participants by email before sharing. Thanks to our dedicated host, Jackson, for helping us successfully organize sharing over and over again. The role of the host is too important to recommend replacement.

Conclusion share

After each shared Q&A, the whole sharing does not end. We’ll discuss the pros and cons of this sharing. Keep up the good, and improve the bad. For example, preparation in advance, time control, PPT production and so on. This is a big improvement for the sharer. Three people must have my teacher, choose its good and from, its bad and change. The audience can also improve themselves from the summary and prepare for their next sharing.

How to Prepare to Share

Record personal shallow view here, if there is insufficient please criticize and correct.

Preparation before Sharing

  • Understand the technical level of the audience, determine the depth of the explanation;
  • Refer to the topic related materials, self-study and demo. Keep the source here and put it in the reference at the end of the powerpoint. Can screen some audience preview information in advance, advance to the host;
  • (Have you ever seen a BOSS give a presentation on stage with a notepad in black letters on a white background displayed on the big screen?)

Making PPT has a lot of superb skills (I make skills slightly clumsy, please find advanced use of PPT students), these skills are used to help share people convey ideas, please be good at using.


  • A picture is worth a thousand words: Multiple stickers can be used to make difficult concepts more accessible to the audience. Pictures should also indicate where they came from.

In the sharing

It’s time to demonstrate the sharer’s control and presentation skills. If the BOSS walks by the door of the conference room and sees a wonderful POWERPOINT presentation and a cheerful presenter, will a promotion and a raise be far behind?

Here are a few sharing requirements and tips.

  1. Ask the presenter to stand up and face the audience (the conference room should have a large screen or projection);
  2. You need to interact with your audience (audience can wander off sometimes, you know);
  3. Control the time (about 40 minutes for sharing), and have another 5-10 minutes for Q&A.
  4. Prepare your powerpoint well and try not to jump out of the powerpoint to type code or consult the official website. This writing things can be screenshots show;
  5. I won’t go into details on many of these techniques: looking around the room, posture, gestures, intonation, and so on. Every detail is a matter of learning, so be prepared and practice.

After sharing

There is usually a big “THANKS” on the last page of the PPT to thank the audience and give the right of speech to the host. Next stage Q&A time. Some sharers also like to host the Q&A session by themselves, which is OK. It depends on personal preference.

conclusion

Technology sharing is very important for everyone and every team. Learning is like rowing against the current, if you do not advance, you will fall back. Keep learning and keep progressing. With you!