Alessandro Di Fiore’s provides a brief history of strategic planning trends and makes an argument for a less rigid and more flexible model. He goes on to review how an agile organization needs to balances bottom up input with their strategic goals.
I have been riding Austin’s trails off and on since moving to town over 15 years ago – and my favorite park remains Walnut Creek. Overall its trails are smooth and fast but it does have an impressive log pile hidden within it that until recently, has always given me pause. While this obstacle looks impressive, in reality it is a timid giant, not too demanding provided one commits (and leans back).
Hitting that pile of logs harder each week has helped me focus on other parts of my life where instead of stopping – I should be peddling harder and holding on tight.
Heather Murphy’s article on gratitude explores the under appreciated benefits of a heartfelt thankyou note - and our reluctance to send to them.
Laying out tasks in an Eisenhower matrix is a useful method to prioritize some tasks and trash others.
I started at GM IT in 2013 and while I only see a slice of the action - the scale is impressive. It is a huge machine and projects are counted by the hundreds, if not thousands…
Ron Lichty on Agile and managing developers
Collection of Ron Lichty’s books, posts, podcasts, and other resources related to managing developers. Of particular interest is how a manager’s role changes when working with an agile team.
When it comes to serving content quickly, network “edge” cache servers can be invaluable - at least when a website’s visitor are located around the world and the site’s servers are in Michigan! Not until recently however was there an option to deploy custom JS code on these servers.
The authors suggest more empathy, better framing of purpose, creative agenda design, and test-driving.
Bill Clark’s analysis and taxonomy of tech debt useful for framing discussions of tech debt and making the best use of limited resources.
Michael Lynch’s two part blog post reflects on pitfalls individuals fall into while conducting code reviews and how to avoid them. Particularly interesting was the successful strategy an experienced developer applied when taking over a troubled review with serious foundational issues. Spoiler - this individual did not lead with issues about code formating.
Useful conversation starters for going beyond simple updates and formalities during one on one meetings with teammates. Connecting their work to something greater will help them find purpose and motivation.
The studies of students and couples perceived contributions is fascinating, as the sum inevitability exceeds 100 percent. Very interesting for those interested in team dynamics.
subscribe via RSS