Talks
Speakers
Events
Topics
Sign in
Home
Talks
Speakers
Events
Topics
Leaderboard
Use
Analytics
Sign in
Suggest modification to this talk
Title
Description
RailsConf 2017: What Comes After SOLID? Seeking Holistic Software Quality by Ariel Caplan You care deeply about code quality and constantly strive to learn more. You devour books and blogs, watch conference talks, and practice code katas. That's excellent! But immaculately factored code and clean architecture alone won't guarantee quality software. As a developer, your job isn't to write Good Code. It's to deliver value for people. In that light, we'll examine the effects of a host of popular coding practices. What do they accomplish? Where do they fall short? We'll set meaningful goals for well-rounded, high-quality software that solves important problems for real people.
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 talk "What Comes After SOLID? Seeking Holistic Software Quality" by Ariel Caplan at RailsConf 2017 addresses the gap between writing good code and delivering value through software development. Caplan emphasizes that the ultimate goal of software development is to create value, not merely to produce well-structured code. He raises critical questions about why developers commit to writing good code and how this impacts software quality. Key Points: - **Value Creation Over Good Code**: Developers should focus on creating value through problem-solving rather than just writing good code. Good code helps in delivering value, but it is not synonymous with quality software. - **Understanding User Needs**: Developers must align their work with actual user needs and business objectives—working to generate revenue, lower costs, or reduce risks. - **Agile's Limitations**: Caplan critiques the Agile methodology, arguing that it has not achieved its goal of bridging the gap between development and business needs. He highlights that trust and effective communication are crucial for a harmonious relationship between developers and business stakeholders. - **The USA Framework**: Caplan introduces a framework consisting of three factors that define software quality: usefulness, sustainability, and accuracy. Each factor is associated with specific questions that developers should consider when assessing their work. - **Usefulness**: Does it solve a problem effectively? - **Sustainability**: Can we continue to develop without unnecessary obstacles? - **Accuracy**: Does the software work as intended? - **Role of Practices**: The talk discusses various software practices that enhance usefulness, sustainability, and accuracy. While traditional coding practices like SOLID principles are important, Caplan stresses the need for user-centered thinking and emphasizes empathy in design. - **Continuous Learning**: Caplan emphasizes the importance of empathy, communication, and understanding business realities as essential skills for software developers. In conclusion, Caplan urges developers to recognize the true purpose of their work as delivering real value to users through quality software. By fostering trust with stakeholders and applying the principles of usability, sustainability, and accuracy, developers can enhance the overall quality of their software products, leading to better outcomes for everyone involved.
Suggest modifications
Cancel
