Mediating style discussions is hard.
Past discussion was mostly passive
Question. In which namespace `B` is defined?
A = Class.new do
B = 1
A::B # => ???
B # => ???
More on the topic https://fili.pp.ru/leaky-constants.html
Are you adventurous enough to use Sidekiq via ActiveJob?
Would you like to hear a success story with a lot of "gotcha" moments?
Would you be interested in seeing a list of best practices digested from over a hundred of background job related code reviews?
Fresh article about an adventure in which I'm fixing a single cop, check it out:
Let's improve thread creation in Ruby by an order of magnitude: https://github.com/ruby/ruby/pull/2227 😍
Posted an article about Open Source, Biochemistry, and Happiness.
Appreciate your feedback.
Posted a small article on Toreman, one-line `Procfile` manager
Converted the Rails style guide and the Ruby style guide to AsciiDoc, too.
Why AsciiDoc? It's hard to write a blog post. It's easy to write an email. AsciiDoc was created to be easy to write in the first place.
Pushed Toreman (https://github.com/pirj/toreman), a one line of shell script Foreman port for tmux.
Went through the open tickets in `rubocop-rspec`, fixed three bugs, added (well, extracted) a new cop.
Did you know that if you declare a constant or a class inside RSpec's DSL, they will be declared globally, and will clash with subsequent declarations?
Vote for it! https://github.com/rubocop-hq/rubocop-rspec/pull/765
Converted RSpec Style Guide from Markdown to AsciiDoc.
AsciiDoctor, which is written in Ruby, does a great job. As a result, the markup is more semantic, and the output is nicer.
Check it out and let me know what you think.
Wondering what you guys think of the renewed RSpec Style Guide.
After a 1.5 break I blogged about my last pull request.
After writing this down, I feel more confident to fix 1335 RuboCop offences in `rspec-core`.
I have a gut feeling it's finally happening, and I'll be able to move on to the next item on my list of planned open source submissions.
Being a niché, performance-oriented, RuboCop cop, AggregateExamples helped one project to shave off some part of its spec suite run, and also with proper techniques to improve its readability.