I've spent an unhealthy amount of time thinking about how to share this so I'm literally sharing the drafts of my thought process to respect the garden-blog concept 😁 I got the opportunity to share this at Xebia 's annual TED-style knowledge exchange and the event was incredible as always. I'm not sure the recording will go online but this page holds the original idea and the final edit of the poem. This talk explored belief systems, focusing on one of the most challenging obstacles we face: the struggle to accept grief, help and continue living fully. The closer the loss, the bigger the smack. I don't know if that ever changes but I think it's worth being grateful for overcoming those moments sometimes. It takes a village: (A love Letter to communities) - Lessons: Noobing through everything in life is how a lot of us are doing and for anyone who had the privilege to learn how to live, what a beauty! What does a toy car, a tea flask and a girlfriend have in co...
Perhaps we haven't had enough learning or sharing opportunities on the topic (over the last 20 years) but we're more connected than before so I do hope we get to hear every voice. A little performance monitoring history teaches that in the early days, software performance was primarily focused on functionality rather than service levels. What Google and similarly large players discovered was a shift driven by the need for systems to not only be functional but also reliable, performant and available. why? increasing complexity of systems (social-technical) and higher user expectations . Do you meet any of the following criteria: Are you working on software? Running on the modern cloud? Do you have two or more stakeholders on your team? Do you have or intend to have customers? at least one? Do you handle sensitive information on or through your software? ... Making this happen depends on a lot of factors and it doesn't have to be complex. At any scale, reliability is ...