Frédéric Trudeau

Drupal GovCon begins tomorrow! Stop by the DrupalEasy table to say hello and learn more about our best-practice-focused long-form #drupal courses!

6

https://lnkd.in/gGZMZDC5 - As a #RubyOnRails developer, you've likely come across situations where forms don't map directly to a single model or models that have complex validation and business logic. This is where the Form Object design pattern comes in! It encapsulates all the logic related to form processing, validation, and data persistence. It acts as an intermediary between the Controller and the Model. Form Objects offer numerous benefits such as encapsulation of form logic, handling composite forms, implementing custom validations, delegating data persistence, and re-usability of logic across different parts of the application.

6

1 Comment

To all my fellow dev leaders, what's something you've learned through your growth that you didn't realize early on? For me, it's been empathy and simplicity. As a dev leader, you're often asked to provide simple answers to complex problems and give estimates of when they'll be ready. This makes up a significant part of the job. To build trust and clarity, you need to empathize with your clients' needs (both internal and external), fully understand the customer need, and platform or service you're delivering on. This ensures you're delivering value and maintaining trust. I've learned to say "I understand" more than I've uttered "are you crazy?!". When I was a junior developer, I tended to overcomplicate problems to justify my expertise. But as I grew and learned from mentors, I realized most people want to know three things: Can it be fixed? When can it be done? What do I need to do? Like a car repair, they want clear, straightforward answers, not technical jargon. With that, rather than outright reject a new feature or revision simply because I didn't want to fix the problem or undo work I've done — I've learned to see every bit of feedback as an opportunity to enhance features and bring things closer to the customer's expectation — a valuable insight in building great products. In delivering, I'm not always perfect (I've learned to be imperfect) and often rethink my approach, but to me this represents growth and persistence. It's about striving to deliver the best results and meeting expectations. Sometimes we have answers right away, but I find my trust goes further when I thoroughly think through the process, even if it means rethinking within reason to ensure we're meeting every expectation above and beyond. This isn't about inefficiency or indecisiveness; it's about delivering the best possible results. So, what's something you've learned on your journey in dev leadership?

11

2 Comments