Scott Streit

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

Kicking off the weekend by wrapping up my latest blog post on how to customize the Spring Boot banner with details from the pom.xml. This was a fun project for me. It's not common to see people customizing the Spring Boot banner, but it's a great way to add unique branding and include useful project information. Please check out my article, if this sounds interesting to you. #SpringBoot #Blog #Programing #SoftwareDevelopment #Java

26

1 Comment

AI - always be willing to challenge it and other digital experts ChatGPT4-o has memory, so you can continue from a response without repeating the original question. This comes in handy when challenging the tool about its answer: Me: Drupal how do I add a custom submit handler to a form so that the original submit handler can execute afterwards? GPT: In Drupal, if you want to add a custom submit handler to a form but still allow the original submit handler to execute afterwards, you can do so by using the #submit property of the form. You don’t need to remove the original handler—just append your custom handler to the list of submit handlers. Me: If submit handlers are executed sequentially why would adding mine to the end of the array cause it to execute first? GPT: You’re correct! I misspoke in my earlier explanation. Submit handlers in Drupal are executed in the order they are added to the #submit array, meaning handlers added later will execute after those added earlier. So if you add your submit handler to the end of the #submit array, it will execute last, not first. I've long recognized the limitations of computers spitting back information it has been programmed to "comprehend." A great example is Google Translation. Try translating an idiomatic sentence and then reversing the languages so that it translates its translation back into your language. The results often do not represent you intended meaning. The ChatGPT example is a fairly innocuous error, despite being 180° off. I did have an occasion, though, where the error was potential deadly. GPS was giving us turn-by-turn directions in a remote part of Iceland one very dark night. It said to take the first turning off a traffic circle (well...roundabout...there wouldn't have been traffic there, ever) and continue for a mile. I took the turn, and after about 200 yards I stopped because even in the darkness, the road ahead looked even darker, and I had this uneasy gut feeling. I got out of the car and walked another 100 feet and discovered the edge of a cliff, no guard rail, with 25-50 foot drop. It turned out that a new turn was added to the roundabout and wasn't yet in the GPS database.

4

Introducing Next.js 15 - Discover the latest features and enhancements for your projects! Explore more in the blog below. #nextjs #reactjs #optimization

28

Get your code into production. One of my pet peeves is when a team develops new functionality QA for months before pushing to production…then are surprised when they try to push to production and (1) 4233 things break and (2) their business counterparts are underwhelmed with the result. My teams generally push to production every sprint - each user story must go into production Developing a muscle for regularly and frequently pushing changes as an IT/data organization forces you to: 1️⃣ Automate: common processes, security checks, quality 2️⃣ Containerize: everything should be reproducible including environments and packages 3️⃣ Decouple: if your deployment breaks it should not affect other teams/deployments 4️⃣ Simplify: deploy less at a time, also reducing risk

5