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're a place where coders share, stay up-to-date and grow their careers.
We strive for transparency and don't collect excess data.