If you go to a developer conference, sponsored by your employer or not, do you take the chance in the coming team meeting to share what you learned there?
For further actions, you may consider blocking this person and/or reporting abuse
If you go to a developer conference, sponsored by your employer or not, do you take the chance in the coming team meeting to share what you learned there?
For further actions, you may consider blocking this person and/or reporting abuse
Pulkit Singh -
Michael Tharrington -
ViitorCloud Technologies -
Grenish rai -
Top comments (4)
Yep - it's a really good way to cement your understanding of what whizzed past at the time - debrief yourself by writing it down for others (we happen to have a corporate wiki for this kind of thing). It typically takes me half as long to summarise as the conference itself.
It's fun to pick out the really wacky/contentious ideas and introduce those at the next retrospective session to get some out-of-our-rut thoughts going, then point the team at the longer written content. Through such means we are now experimenting with immutable components, serverless technologies, service meshes and sidecars..
Thanks a lot for your answer. In the end, I also decided and was explicitly asked by the management to hold a retrospective. Will come soon.
We where all sooo hungover
Where? You went to the Global Week of Beer Retreat?