Small Acts of Leadership | Book Series

Overview:

In business today, there is no offline and there is no downtime. Professionals are both exhausted and depleted. Being constantly tethered to our work through technology makes us overwhelmed and shortsighted, and deprives us of time for meaningful reflection or thoughtful connection to our professional communities, and often even to our own families.  

For us to thrive-not simply survive-in this accelerating economy, we need to adopt small, intentional behaviors and practice them each day. From simply taking care of our rest and exercise to building our self-confidence and embracing challenges, author Shawn Hunter’s latest book Small Acts of Leadership will guide you through a series of incremental steps you can take to build a stronger version of yourself and make a broader impact in the world.  

Weaving in personal life stories and meaningful interviews with business leaders around the world, Hunter presents the reader with twelve critical competencies that are consistently present in the daily behaviors of today’s most successful leaders.

Author:   

G. Shawn Hunter

Published In:

19 December 2016

Non-Solo Development | Glossary

Definition:

In Extreme Programming (XP), pair programming is a practice that suggests two developers should work together sharing one keyboard as they code. This is also a type of code review/ design in real-time as one person watches when the other codes. The key benefit is better quality coding before the code is generated.            

Non-solo development produces higher quality code, code with fewer defects, and less technical debt.  Most all of us have seen the chart that shows the cost of a defect growing exponentially during the development lifecycle.  Fixing a bug in a maintenance mode requires someone (or a pair) to wrap their brain around often complex algorithms in order to understand the logic, make the repair, and not break something else.  This is far more costly later, rather than when the code is “fresh in your head”. Having a second set of eyes present while code is being authored often catches these bugs before they happen.  

Further Reading:

Book: Disciplined Agile Delivery by Scott W. Ambler and Mark Lines