Suggest modification to this talk

Title

Description

Tobias Pfeiffer — Do You Need That Validation? Let Me Call You Back About It

Contents

0:24 Intro about Lviv and community
1:41 Let's build an app to organize an event
3:20 Let’s write an auditory test 
5:45 What does a smell mean? 
7:05 Let's talk about validations
8:45 The example of validation: doctor’s appointment
12:22 How many ways are there to change in email at gitlab?
14:03 Why are we doing this?
15:17 What is Rails Affordance?
15:33 “Fat Models Skinny Controllers”
18:15 Let's take a look at a user model
21:30 Do you need that validation? Let me call you back about it
22:23 What did we identify as problems?
22:00 What does Rails offer to us?
25:40 Form Objects and Plain ActiveModel
29:40 Changesets
34:58 Separate operations and validators
36:57 What can you take away from all of this?
40:20 Alternatives
41:53 Q&As

Let's chat, meet, and share our ideas via all the social media:

Join us on Facebook: https://bit.ly/2WjAgVb 
Tweet a bit with us there: https://bit.ly/2XmndyK 
Follow us on LinkedIn: https://bit.ly/2MmSn8j 
Hop in some cool articles here: https://bit.ly/2IcMgOx 
Our Instagram account:  https://bit.ly/2QDZCaf 
Become a register member on our site and get all the benefits: https://bit.ly/313cImj

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 titled "Do You Need That Validation?" features Tobias Pfeiffer, presenting during the Pivorak Conf 3.0 in Lviv. The main theme centers around the complexities of validations in software development, particularly within Rails applications. Tobias discusses various challenges developers face when implementing validations and highlights ways to improve code maintainability.

**Key Points:**
- **Community and Events:** The session begins with an appreciation of the Lviv community and the importance of organizing events, leading to the idea of creating an event management app. 
- **Event Management App Development:** A prototype app is proposed which simplifies event organization by reducing redundancy in date entries while addressing potential pitfalls related to validation hooks. 
- **Challenges with Validations:** Tobias explains how overly complex validations can obscure issues, using the example of a doctor’s appointment to illustrate how they might lead to unexpected errors in the system. 
- **GitLab User Model Case Study:** A detailed analysis of the user model at GitLab is presented, showcasing how complex conditional validations can entangle logic and make debugging difficult. 
- **Affordances and Simplification:** There’s a strong emphasis on the concept of "affordances," promoting the idea that software should communicate its requirements clearly without unnecessary complexity in validation logic. 
- **Overcomplication of Models:** Highlighted are the risks of adding too many responsibilities to models, which can cause clutter and decrease maintainability. 
- **Service Objects and Form Objects:** Alternatives to handle validations effectively include implementing service and form objects, separating the validation logic from the core user model and ensuring clarity.  
- **Frameworks and Libraries:** Recommended tools like Active Type and techniques for managing applications with distinct contexts help improve readability and maintenance of code. 
- **Main Takeaways:** Recognizing the burden of complex validations leads to a call for better design approaches that enhance the clarity, maintainability, and scalability of software. 
- **Final Remarks:** Tobias encourages developers to reflect on their implementations, advocating for structured separation of concerns to advance their projects effectively.

Cancel