Talks
Speakers
Events
Topics
Search
Sign in
Search
Home
Talks
Speakers
Events
Topics
Leaderboard
Use
Analytics
Sign in
search talks for
⏎
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 tradeoffs we’re making together. Help us caption & translate this video! http://amara.org/v/GWId/
Date
Summarized using AI?
If this talk's summary was generated by AI, please check this box. A "Summarized using AI" badge will be displayed in the summary tab to indicate that the summary was generated using AI.
Show "Summarized using AI" badge on summary page
Summary
Markdown supported
The video "Humane Development" presented by Ernie Miller discusses the importance of acknowledging the human aspect of software development amidst various methodologies like Agile, Scrum, and Kanban. Miller argues that while these processes aim to streamline development, they often dehumanize individuals involved, reducing them to mere resources or objects, which adversely affects team dynamics and productivity. Key points discussed include: - **Personal Experience**: Miller shares his transition to the role of Director of Engineering at Invisium, highlighting the pressure and the realization that if things went wrong, it was ultimately his responsibility. - **Cultural Considerations**: He reflects on the type of work culture he values, emphasizing the significance of human interaction and empathy in software development. - **Dehumanization Through Processes**: Miller recounts an experience with a CEO who viewed team members as objects within a process, leading to an oppressive environment. - **The Concept of "Humane Development"**: He introduces the term to stress the importance of retaining the human aspect in development methodologies, arguing that software development should ultimately serve people, not just processes. - **Issues with Current Methodologies**: The discussion touches on how Agile practices have been misinterpreted over time, with a focus on measurement, predictability, and control, overshadowing the underlying values of collaboration and flexibility. - **The Importance of Empathy and Communication**: Miller advocates for empathy, honesty, trust, and autonomy as foundational values in a healthy work culture, asserting that effective communication can bridge gaps between business needs and development. - **Sustainability vs. Hustle**: He critiques startup culture’s glorification of hustle, emphasizing that sustainable work approaches are more beneficial than simply moving fast and breaking things. - **The Question of "Why"**: Emphasizing the importance of understanding the underlying reasons for tasks, Miller encourages developers and managers to always seek the rationale behind tasks to ensure meaningful productivity. Miller concludes that software development is fundamentally about humans working with humans for humans, which requires a shift away from mere process adherence to a more humane approach. His key takeaway is the need for a cultural transformation within organizations to prioritize human values over rigid processes, fostering environments where innovation and empathy can flourish.
Suggest modifications
Cancel
