markdown guide

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.

Classic DEV Post from May 4

The secret that the fonts industry doesn't want you to know

Finally the story of CSS's most unsung hero

Sandor Dargo profile image
Happy father. Blogger. Developer. Amateur of graph databases.