Ruby Video
Talks
Speakers
Events
Topics
Leaderboard
Sign in
Talks
Speakers
Events
Topics
Use
Analytics
Sign in
Suggest modification to this talk
Title
Description
By Ernie Miller Agile. Scrum. Kanban. Waterfall. TDD. BDD. OOP. FP. AOP. WTH? As a software developer, I can adopt methodologies so that I feel there's a sense of order in the world. There's a problem with this story: We are humans, developing software with humans, to benefit humans. And humans are messy. We wrap ourselves in process, trying to trade people for personas, points, planning poker, and the promise of predictability. Only people aren't objects to be abstracted away. Let's take some time to think through the trade offs we're making together. Help us caption & translate this video! http://amara.org/v/G6iR/
Date
Summary
Markdown supported
The video 'Humane Development' by Ernie Miller, presented at RailsConf 2015, addresses the intersection of human elements and software development methodologies. It emphasizes the messiness of human interaction within technical processes and the pitfalls of dehumanizing team members in pursuit of predictable outcomes. Key points discussed include: - **Responsibility and Accountability**: Ernie Miller, as the Director of Engineering at Invisium, shares the pressure and accountability he feels in his role, acknowledging that workplace issues often lead to employee turnover. - **Humanizing Software Development**: The speaker stresses that developers and teams are not just resources or abstractions; they are humans contributing to a collaborative environment. He coined the term 'humane development' to encapsulate the idea that software development should prioritize compassion and understanding. - **Agile Methodology Critique**: Miller critiques the common adoption of agile practices without their foundational principles, noting how organizations often revert to old processes despite the agile mindset emphasizing individual interactions over rigid procedures. - **Culture of Urgency**: He conveys the dangers of working under constant urgency, urging teams to evaluate the actual importance of deadlines and the potential damage of hurried decision-making. - **Importance of Environment and Autonomy**: Stressing the need for a work environment that fosters autonomy, Miller highlights how organizations should trust and empower their teams instead of creating constraints. Miller's insights are grounded in personal anecdotes about experiences that illustrate the emotional dynamics at play within teams. A significant moment involves a previous CEO’s reductive view of team members as mere resources, highlighting the detrimental effects of such an approach. He underlines the importance of connection, empathy, and dialogue to build a healthier workplace culture. In conclusion, Miller calls for a reconsideration of methodologies that prioritize human factors, advocating for transparency and trust in teams. He suggests that recognizing our shared humanity can lead to healthier environments conducive to innovation and productivity. The discussion resonates with industry trends where employee well-being is integral to long-term success, urging collective action towards a humane approach in software development.
Suggest modifications
Cancel