A list of bugs in her refactored code: 1) items without a special case are treated as Sulfuras, not Normal. Easy fix. 2) normal items can be reduced below 0 quality if odd after expiry date. Once reduced below 0, will continue deeper into the negatives 3) aged brie can increase above 50 quality if even after expiry date. Once increased above 50, will continue higher 4) backstage pass can increase above 50 when days remaining is less than 10. This corrects after the concert occurs 5) Conjured items can be reduced below 0 if it begins with an odd number quality. Once reduced below 0, will continue deeper into the negatives 6) the goblin in the corner may get mad (he has the item class and she has basically remade her function into an item repackager). 1 is easy to fix, the no-match case should return a Normal object 2-5 is the same basic error just duplicated. It just needs a set to 0/50 end to the functions. 6 is a diplomacy check against your fellow programmer.
I'm designing a multilanguage multisite site with CMS for content creation. As an experienced Django developer, I think Django with Python can help with the custom tools needed. Thanks for the video.
Amazing presentation, this definitely gave me a lot of insights on how to start investigating memory leaks issue I'm currently facing. Very nice examples, details and explanations. Thanks a lot!
You can see the slides and you can hear the talk if you could somehow trim the annoying Jazz intro and outro this would be perfect even if you can't see Nick pace back and forth behind the lectern as he talks.
Really cool, I love Elixir, but using it for a one shot to resize images it really overkill, specially if as told this was something needed ASAP. 3M records is manageable, extract it in a file, split it in N*k files, write a batch script that download the images, process them and upload them, send it to N machines, start k processes that run concurrently on each machine and wait. If you have 5 machines with 20 cores, even at 1.6s/image (probably can be improved with batch processing), it will only take 13 hours, the next day your images would be ready. Enjoy your free time to learn more about Elixir.
Great talk, worthy of every Rails dev time. 9:30 The liberating realization that resources need not map 1-to-1 to models. You can have actor-specific "window" resurces into underlying data, or PORO-backed resources (SessionsController). 18:11 Derek touches on DDD's Ubiquitous Language idea as a rule to help disambiguate what #process action might be doing. An alternative approach could be to use another powerful tool from DDD - actor analysis, i.e OrdersController is probably too generic and then the ShipmentsController also. Shipping where, between warehouses, to customer? An actor-identifying namespace might be missing - Inventory::OrdersController etc. 18:58 Welcome to controller hook hell. Derek touches on this being bad, but does not go into how to make things better. I do dev.to/epigene/stop-abusing-beforeaction-48di 34:20 ""There's no reason a collection of objects can't be a resource". Yup, in DDD they're called Aggregates.
With the recent advancements in deep learning the state of the art for this topic has hugely changed. Unfortunately or not, Ruby is nowhere near to where the interesting things are happening.
Sandy Metz🥰 i'm in love!! since i read his book Practical Object-Oriented Design. I still think about her whenever i heard the term Ruby or smalltalk. Really 😁
Seems like a lot of complication. I never really went for it. The only selling point to me was replay ability. However the extra complication isn't worth it.
I was at this talk. It always felt like magic when Jim Weirich explained something to you, seemingly Gandalf had just whispered a spell in your ear that let you understand things beyond your own comprehension. What a teacher!
