@tamouse You don't want to make a typo in an instance var usage.
@nakilon It's open source by the way ;)
RSpec's implicit block cryptic expectation syntax will disappear from RSpec 3.9.0 https://github.com/rspec/rspec-expectations/pull/1125
Also, I've joined the RSpec Core team! 🙌
@postmodern There are some neat jobs there, not specifically ruby. Everyone are looking for full-stacks those days anyway.
@postmodern stackoverflow.com/jobs, weworkremotely.com, jobs.github.com ?
This talk is brilliant https://vimeo.com/9270320
All about the lack and overlook of fundamental research in different aspects of practical programming.
It touches so many topics that it would hardly fit into a toot limit.
Just watch it.
Mediating style discussions is hard.
Past discussion was mostly passive
Seems they've added it before I've made a correction to the article basing on your lexical scope remark.
@james You're right, the wording it's defined in top-level namespace is incorrect, should be the same scope as the block containing it. 👍
@james Couldn't find a better answer than this https://github.com/rspec/rspec-core/issues/2181#issuecomment-190535022
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
@james There's a cop for that™
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:
@ioquatix There's a good explanation why it should go to stderr in "A Research UNIX Reader: Annotated Excerpts from the Programmer’s Manual":
Let's improve thread creation in Ruby by an order of magnitude: https://github.com/ruby/ruby/pull/2227 😍