October CincyRb - Jim Weirich on Decoupling from Rails

[@sebastianmitterle3779]

Fantasy tests, XD Love the name!

[@RubyLoveIO]

If you liked this talk about Ruby from my friend Jim, check out this one on removing conditionals for your ruby code! kzbin.info/www/bejne/gJmsiqpnjpyjj5I One of my favorite videos by Jim. Teasing out domain logic from rails is a worthy goal. If you want to learn how to do this kind of rails development hit me up. Jim and I have the same favorite Uncle.

[@natewallis1]

hey.. whats the best way to contact you

[@RubyLoveIO]

Nathan Wallis rubylove.io

[@jcabas]

Hey Ruby Love you know what's that VIM plugin Jim uses to create methods?

[@RubyLoveIO]

Jonathan Andrés Cabas Candama Jim didn't use Vi all that much when he was alive. He used EMACS. (read below the split for links) However, you can get a plugin that does this in vim. Ii haven't found one I like enough to use a lot (I do it by hand) but you can get some good ideas from: www.google.com.mx/search?q=vim+refactor+ruby&oq=vim+refactor+ruby&aqs=chrome..69i57.4359j0j7&sourceid=chrome&es_sm=91&ie=UTF-8

[@jcabas]

Ruby Love Hey Thank you.

[@milesrout]

RIP

[@NeilErnst]

Anyone know if the Omnigraffle models are public anywhere?

[@Zhaynoth]

I didn't get the biz part. What kind of stuff should go into biz?

[@RegularCupOfJoe]

Business logic. The stuff that represents a business or technical process.

[@Zhaynoth]

Thanks Glass. But how long should be the business or technical process that goes there? I mean, if there is a large logic process that involves doing tasks on other models, how all that logic should be placed along runners, biz models, models, and repositories?

[@RegularCupOfJoe]

I'll say it this way: keep logic cleanly organized. Suppose in some process that I have, I need to determine a person's birthday to send them a birthday greeting card and I need to send them a reminder card to pay their rent. (Silly example, I know, but let's stay with it.) I would have one flow through my system that is responsible for getting the person's birthday, determining if his (or her) birthday is a few days away, and sending the birthday greeting card. I would have another system that focuses on getting the person's rent policy, determine if rent is about due, and sending the rent due reminder. Even though these are all a part of how my business operates, they are separate operations within my business. So I should keep them separate from each other in my code. There's a pattern in software called "the Single Responsibility Pattern" (it's on Wikipedia), and it says that code is easier to develop and maintain, and typically more performant, when each "unit" of work is has one and only one responsibility. So, birthday greetings are a high level "unit" of work in my business, so I ought to write it to be really good at sending birthday greetings. The same is true of rent due reminders. And birthday greetings and rent due reminders should little to no knowledge of each other in terms of code. Does that sort of make sense? Please feel free to ask more questions; I quite enjoy talking coding patterns, design, and architecture.

[@JoshSandlin]

What testing framework is he using?

[@linuxgirl_]

+Josh Sandlin I think it's just Rspec with some basic extensions, e.g. rspec-given.

[@dovitart]

3301