This week, I've made significant progress, completing about 80% of the second email for my Short Ruby Email Courses. This email is about into the syntax of the endless method.
My focus was on providing practical insights. I explored the history of feature requests submitted to reduce the number of `end` we write and understand what would be the benefits of using this new #Ruby syntax.
It is the middle of the week so maybe now it is a good time to take a small break and reflect on what you could NOT implement.
Not everything you think should be implemented is essential now. Some things can be omitted or delegated for later.
I was just doing some benchmarking of a bit of ruby code, comparing `value.digits(32)` to an explicit while loop that does the same thing, and decided to try it with `--yjit` too.
* Normal ruby -- native method was more performant, although not by a whole lot
* with `--yjit` the ruby loop was better than the native method.
https://gist.github.com/copiousfreetime/fe69dcdde98c7bcb0858095223515df6
"Small methods ease maintenance. They let you isolate assumptions.
Code that has been written with the right small methods requires the change of only a few methods to correct or enhance its operation"
- Source: Smalltalk Best Practice Patterns
What are you planning to develop with #Ruby or #RubyOnRails this week?
For my side project, I plan to continue with writing the second email for the #ModernRuby #EmailCourse: "Endless Method Definition"
