Suggest modification to this talk

Title

Description

RailsConf 2019 - I know I can, but should I? Evaluating Alternatives by Kevin Murphy
_______________________________________________________________________________________________
Cloud 66 - Pain Free Rails Deployments
Cloud 66 for Rails acts like your in-house DevOps team to build, deploy and maintain your Rails applications on any cloud or server.

Get $100 Cloud 66 Free Credits with the code: RailsConf-19
($100 Cloud 66 Free Credits, for the new user only, valid till 31st December 2019)

Link to the website: https://cloud66.com/rails?utm_source=-&utm_medium=-&utm_campaign=RailsConf19
Link to sign up: https://app.cloud66.com/users/sign_in?utm_source=-&utm_medium=-&utm_campaign=RailsConf19
_______________________________________________________________________________________________
You can use a hammer to drive a screw into wood, but I’d recommend a screwdriver. Why? And when is a hammer the better option? This talk will propose a framework to use when comparing alternative technical choices. I won’t decide for you, but will leave you with a structure to apply in your decision-making process.

The ruby toolbox is vast. While Rails provides a default experience, it leaves plenty of room for alternatives. In learning how to do something, you may uncover different ways to accomplish the same goal. Determine which tool fits best in your situation with these lessons.

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 "I know I can, but should I? Evaluating Alternatives" by Kevin Murphy at RailsConf 2019 explores the complexities involved in making technical choices in software development. Kevin uses the metaphor of selecting between different tools (hammer, screwdriver, etc.) to illustrate how various factors influence decision-making. He proposes a framework for evaluating alternatives based on four key criteria: impact, cost, maintenance, and consistency.

Key points discussed include:

- **Making Choices**: The importance of making informed technical decisions rather than relying on instinct or popular opinion.
- **Weighted Scoring Model**: Introducing a systematic approach for evaluating options through a weighted scoring model to facilitate better decision-making. This includes determining what criteria matter most to the team.
- **Criteria for Evaluation**:
  - **Impact**: Assessing how decisions affect the team and codebase, along with potential non-functional requirements like performance and accessibility.
  - **Cost**: Understanding the risks associated with solutions, including dependencies on third-party libraries versus developing in-house solutions.
  - **Maintenance**: Considering the long-term implications of choices, including how easily future team members can work with the code.
  - **Consistency**: Finding a balance between adhering to established practices and integrating new approaches, ensuring the codebase remains comprehensible to new team members.
- **Example Scenarios**: Kevin illustrates his points through practical examples, such as a tool for food scientists at Hormel, where the audience evaluates alternatives for implementing specific functionalities.
- **Final Thoughts**: The conclusion emphasizes the necessity of evaluating choices based on all four criteria while recognizing the context of a problem and being adaptable in the decision-making process. The talk encourages developers to engage in discussions with their teams to find solutions that align with both technical and business needs.

The core takeaway from Kevin's talk is that while it’s important to identify the right tool for the task, understanding the implications of each choice and collaborating with stakeholders is crucial for sustainable software development.

Cancel