Ruby Central is a non-profit organization that supports and advances the Ruby programming language and a welcoming and diverse worldwide Ruby community. We organize the annual software conferences, RubyConf and RailsConf, to which this video channel is dedicated. Learn more | www.rubycentral.org
RubyConf is the Ruby community's Fall celebration of all things Ruby! Ruby enthusiasts gather to enjoy detailed talks about exciting new projects; meet and network with other Ruby developers; and hear from the community's leading minds, including Yukihiro Matsumoto ("Matz"), the creator of the Ruby language.
RailsConf is the world's largest gathering of Rails developers, brought together in the Spring to further discuss and learn about building, managing, and testing Rails applications. With a specific focus on Rails, conference topics can range from new users to administration to advanced techniques.
Brilliant Amir. Really inspiring. Everything about your approach and why and how. And just came across your work again via the Ruby Remote podcast today.
We found a good approach is to place for each class just one `call` method: - for smaller repo eg. `app/services/invoice_service/create_invoice.rb` (monolith) - for medium repo eg. `components/finance/invoice_service/create_invoice.rb` (modulith)
I think ruby & rails should be updated continuously as soon as a new version is out. obviously this is done in development and with its own ticket and then let the team know of the results so if there is a breaking change have the entire team upgrade it and not just one, I'm looking at a bunch of companies who kept old unsupported databases & dependencies, I've been though a lot of these teams.
Uhh.. That's just lazy OOP, with unnecessary fluff when all the good terms are already the without creating classes like "SomethingCreator", "SomethingDoer", etc.. Presumably in this case User class "has_many :orders". Extend the relationship with a module: "has_many :orders, extend: UserOders". In that UserOrders create your variant of "create" method. Since given example does auth, charge and emails, let's call method "place". So "user places an order". In that method you can access the owning side of relationship (in our case instace of User) through "proxy_association.owner". That's it.. And then your controller code will looks something like: "order = user.orders.place(verified_params); if order.persisted? redirect_to(...) else render :new" (this is bit of a pseudocode since youtube comment section won't allow good code formatting). There's little bit of trickery in error handling, but everything is there. Note that relationship can have multiple extending modules. If one module starts becoming unwieldy - you can always split in multiple modules by some sort of "theme".
Great conference we are lucky to have Amir and dragonruby toolkit. Im considering making a game in because it seems very pleasant to code in. Keep going dragonruby.
No idea why rails has to be so absurdly complicated. In react, you never once have to think about the details of what’s going on in the AJAX requests because all that detail is abstracted away from developers and it just.. works. Having to understand all the nuances of low level details just to write a front end in exchange for not having to write JavaScript is NOT a good trade off at ALL. That’s like saying we can write all our clientside code in assembly but at least there’s no JS!
You should try building a full stack app with both approaches and you will realise that Turbo gives you much better dx and abstracts away more implementation details than react spa’s do.
That's actually slow. You can get about 10 times more by batching. Transform all your sprites on cpu and put them into a triangle array that you hand over to SDL_RenderGeometry() that you just call once per frame (or as many times as you have batches).
I think it’s a mindset difference people who like monolith can only like this. React is micro service mindset people who like to breakdown mammoth into rats.
Here's the "same" presentation from N. Means but with better video (no stupid rubycon burned in ad): ru-vid.com/video/%D0%B2%D0%B8%D0%B4%D0%B5%D0%BE-3mhLT3boo6A.html
I think the author is doing a fabulous job taking the watcher along for the ride and letting them have the same epiphanies. But I also think there’s more places where mocking is necessary and beneficial and would encourage the reader of this comment to look up some of the talks by Sandi Metz about the magic rules for testing.
