Welcome to another VSHN.timer! Every Monday, 5 links related to Kubernetes, OpenShift, CI / CD, and DevOps; all stuff coming out of our own chat system, making us think, laugh, or simply work better.
This week we’re going to talk about the first line of the Agile Manifesto: individuals and interactions.
1. It’s unavoidable; after a certain age, most IT professionals ask themselves questions about their career. Or at least they might just feel tired of being asked the same stupid questions over and over again. Anyway, if you are looking for career advice, Karl Hughes created a list of 23 alternative career paths for software developers to grow into, and we’re sure you’ll find it useful. (Disclaimer: the author of these lines chose the first entry in the list!)
2. There’s a whole category of self-help books and blog posts with lists of „habits of successful people“ but they all mostly boil down to the same recipes. Instead we prefer to focus today on this simple piece of advice by Mattias Geniar: just slow down. Let’s think before acting, let’s learn to have patience, and let’s drive our careers as a marathon, not as a sprint.
3. The COVID-19 pandemic is sadly still active and expanding across the world. We have already talked about working from home in this series, but as this is still relevant for many of us, here’s a list of 7 quick tips by Time Magazine to share much more enjoyable online meetings. Stay safe and use a mask when in public places!
4. Crises happen; it’s only a matter of time. The important is to face them as a team, and to learn enough from them so as to not to repeat them in the future. Take for example Slack and their recent outage on May 12th. Their strategy can be summarized as „All Hands on Deck.“ In the same register, don’t miss the post-mortem of the Cloudflare outage last Friday, and then learn why it’s better to optimize for MTTR instead of MTBF.
5. The tool of the week is PACE, a minimalist project management tool which has recently moved into public preview mode. It looks extremely polished and simple to use, and thanks to its integration with GitHub, it will certainly be useful to many teams out there.
How do you structure your teams? How much flexibility do they have to organize themselves? Do you have any tips you would like to share with the community? Get in touch with us through the form at the bottom of this page, and see you next week for another edition of VSHN.timer.