Culture
To Build a Top Performing Team, Ask for 85% Effort 6 minutes read.
Greg McKeown will make you think about how you work, how you create a sustainable working habits for yourself, and if you're a manager or a leader - how you influence your environment. Intensity and effort are incredibly hard to measure in software development. It's important to discuss the outcomes we seek and nurture a conversation around managing stress and whether we think we're in a healthy place. I expect the answer always to be "no, there is a lot of stress" if you're working for a successful company. But it's the controls you need to focus on - Do we openly discuss it? Do we try to reduce it? Do we make it okay to acknowledge it? Do managers adjust things over time to change stress levels? Do we get people to feel in control of where to push themselves harder and when to take a step back and relax? Do we talk about how they rest and sleep after work hours (not from a judgemental place, but to create awareness)?
Read it later via
Instapaper.
Share
it via
Twitter
or
email.
What Is the Right Level of Specialization? For Data Teams and Anyone Else 5 minutes read.
"People are spending way too much time working on things that have nothing to do with their business. We have come a long way, but I still see people wasting way too much time debugging YAML, waiting for deployments, or begging the SRE team for help." -- Erik Bernhardsson discusses the tradeoffs when hiring tools-oriented versus goal-oriented people. No doubt that some tools introduce overall simplification for the users while they also increase complexity for the maintainers, which requires specialization. It's unavoidable. It's a worthy discussion to see where the balance is not serving the business and make adjustments to the tools you leverage and the people you need.
Read it later via
Instapaper.
Share
it via
Twitter
or
email.