Day-to-day
Knowledge
Sharing

BenedekGagyi

@

  • Continuous learning
  • Code base
  • Architecture
  • Project
  • Culture
  • Day-to-day communication

Knowledge sharing

  • Language barrier
  • Experience barrier

Common language

  • Fit content to audience
  • "Important" is relative

Shared motivation

  • No questions != Understanding
  • Understanding != Practice

Knowledge without exercise

CSS
IS
AWESOME

  • Teamwork is a skill...
  • ... and it's the most important one
  • "top predictors of success are being a good communicator in a team where you feel emotionally safe"

Intern stories

  • Crash courses are cool ...
  • ... if you do a follow-up

Pivoting your carrier is hard

  • Presentations don't work
  • "Exchange student" programs do

Cross-team knowledge sharing is hard

Use your tools the right way

  • KISS
  • Share your successes and fails

Stand-up meetings

  • KISS
  • It's not a QA tool
  • Poor mans pair programming

Code review

Meetings

?

  • Great opportunity to share knowledge

Interview

Continuous learning

{t_s * v_l \over m_{sl}} \geq 1
ts∗vlmsl≥1{t_s * v_l \over m_{sl}} \geq 1
t_s -
ts−t_s -
v_l -
vl−v_l -
m_{sl} -
msl−m_{sl} -

time available for studying

speed of learning "stuff"

amount of "stuff" to learn

Continuous learning

{t_s * v_l \over m_{sl}} \geq 1
ts∗vlmsl≥1{t_s * v_l \over m_{sl}} \geq 1
  • Make more time for studying
  • Improve learning speed
  • Manage your backlog

Thank you!

BenedekGagyi

@

deck

By Benedek Gagyi

Made with Slides.com

deck

  • 658

More from Benedek Gagyi