The software craftsman : professionalism, pragmatism, pride

About This eBook
Title Page
Copyright Page
Contents
Foreword
Preface
	About This Book
Acknowledgments
About the Author
Part I. Ideology and Attitude
	1. Software Development in the Twenty-First Century
		Seniority
		A New Reality
	2. Agile
		Process-Oriented Agile Disciplines
		Technical-Oriented Disciplines
		What Is It to Be Agile?
			A Game Changer
			People Empowerment
			Professional Evolution
		Agile Manifesto
			Principles Behind the Agile Manifesto
		The Agile Transformation Era
		The Agile Hangover
			A Partial Transformation
			But It’s Not All Bad News
		Agile Versus Software Craftsmanship
		Summary
	3. Software Craftsmanship
		A Better Metaphor
		What Does Wikipedia Say?
		A More Personal Definition
		A Shorter Definition
		Beyond Definitions
		Craft, Trade, Engineering, Science, or Art
		Software Craftsmanship History
			The Software Craftsmanship Summit
			Crossing Borders
			Craftsman Swap
			Software Craftsmanship Communities
			The Software Craftsmanship Manifesto
			The Manifesto
		Summary
	4. The Software Craftsmanship Attitude
		Who Owns Your Career?
			Employer/Employee Relationship
		Keeping Ourselves Up to Date
			Books, Many Books
			Blogs
			Technical Websites
		Know Who to Follow
			Social Media
		Practice, Practice, Practice
			Katas
			Pet Projects
			Open Source
			Pair Programming
		Socialize
		Deliberate Discovery
		Work-Life Balance
			Creating Time
			Focus: The Pomodoro Technique
			Balance
		Summary
	5. Heroes, Goodwill, and Professionalism
		Learning How to Say No
			An Epic Failure
			Lesson Learned
			Being Professional
		Providing Options
			An Unexpected and Viable Option
		Enlightened Managers
		Summary
	6. Working Software
		Working Software Is Not Enough
		Looking After Our Garden
		The Invisible Threat
			Hostage of Your Own Software
			Hire Craftsmen, Not Average Developers
		The Wrong Notion of Time
			A Technical Debt Story
			A Busy Team with No Time to Spare
			The Unit Test Task Card
			Using Time Wisely
		Legacy Code
			A Change in Attitude
			Personal and Client Satisfaction
		Summary
	7. Technical Practices
		The Right Thing versus the Thing Right
		Context
		Extreme Programming History
		Practices and Values
			Adding Value through Practices
		Pair Programming
		Accountability
		Pragmatism
		Summary
	8. The Long Road
		A Tale from a Brazilian Teenager
		Focus and Determination
			But What if We Don’t Know Where We Are Going?
		Job as Investment
		Autonomy, Mastery, and Purpose
		Career Inside Companies
		Summary
Part II. A Full Transformation
	9. Recruitment
		An Ordinary Job Description
		Too Busy to Interview
		No Job Descriptions
			What if a Job Description Is Needed?
			A Job Is Not Just a Job
		Recommendations
		Community Involvement
		Defining Effective Filtering Criteria
		Proactive Recruitment
		Summary
	10. Interviewing Software Craftsmen
		A Business Negotiation
		Identifying Productive Partnerships
			A Hiring Company’s Perspective
			A Candidate’s Perspective
		Good Interviews
			The Right Focus
			Mind-Mapping a Conversation
			Pair-Programming Interview
			Bring Your Own Computer
			Tailor-Made Interviews
		Taking a Punt
		Hiring for an Existing Team versus Hiring for a New Team
		Pre-Interview Coding Exercises
		Everyone Should Know How to Interview
		Developers Must Interview Developers
		Summary
	11. Interview Anti-Patterns
		Don’t Be a Smart-Ass Interviewer
		Don’t Use Brainteasers
		Don’t Ask Questions to Which You Don’t Know the Answers
		Don’t Try to Make the Candidate Look Like a Fool
		Don’t Block the Internet
		Don’t Code on a Piece of Paper
		Don’t Use Algorithms
		Don’t Conduct Phone Interviews
		Summary
	12. The Cost of Low Morale
		The Agile Hangover: Low Morale
		The Cost of Employing 9-to-5 Developers
		Constrained by Lack of Motivation
		Injecting Passion
		Summary
	13. Culture of Learning
		Wrong Motivation
		Creating a Culture of Learning
			Start a Book Club
			Have a Tech Lunch (Brown Bag Session)
			Have Group Discussions (Roundtables)
			Switch Projects for an Iteration
			Conduct Group Code Reviews
			Have Hands-On Coding Sessions
			Start Internal Communities of Practice (CoP)
			Encourage Pet-Project Time
			Engage with External Technical Communities
		What if Others Don’t Want to Join In?
			Be an Example
			Focus on Those Who Care
			Don’t Force
			Don’t Try to Change Everyone
			Avoid Consensus Delays
			Don’t Ask for Authorization
			Don’t Complicate
			Establish a Rhythm
		Summary
	14. Driving Technical Changes
		Identifying Skepticism Patterns
		Be Prepared
		Where Do We Start?
			Establish Trust
			Lead by Example
			Choose Your Battles
			Iterate, Inspect, and Adapt
		Fear and Incompetence
		How Do I Convince My Manager?
		How Do I Convince My Team to Do TDD?
		Facing the Skeptics
			The Ivory-Tower Architect
			The Wronged
		Should We Really Care about All That?
		Summary
	15. Pragmatic Craftsmanship
		Quality Is Always Expected
		Busting the “Expensive and Time-Consuming Quality” Myth
			Do We Need to Test-Drive Everything?
		Refactoring
		The “One Way” of Developing Software
		Helping the Business
			A Simple and Quick Solution
		Software Projects Are Not about Us
		Great Versus Mediocre
		Four Rules of Simple Design
			Design Patterns
			Refactoring to Patterns
		Craftsmanship and Pragmatism
		Summary
	16. A Career As a Software Craftsman
		Being a Craftsman
			Honesty and Courage
		Career Progression
			Different Ladders
		Roads and Milestones
			Building Our Careers, One Job at a Time
			What if We Don’t Know Where We Want to Go?
		Job Diversity
		The Mission
A. Craftsmanship Myths and Further Explanations
	Software Craftsman versus Software Developers
	Elitism
	Apprentice, Journeyman, and Master
	Master Craftsman
	Narrow Focus
	Craftsmanship versus XP
	Attachment to Practices
	Agile Coaches and Managers
	Software Apprenticeships
	The Problem with Metaphors
Index