James Adam @james@ruby.social

@jeromedalbert it could be that `db:migrate:redo` uses the `db:migrate` task internally, which then Rake will helpfully not run a second time; try running with `--trace` to see.

That said, I am pretty confident you can still get it done with only two invocations of `rake`, instead of three... 😄

@jeromedalbert how about ‘rake db:migrate db:migrate:redo db:test:prepare’? Would that achieve the same thing but only loading the Rails environment once?

For the first time in quite a while, I wrote a non-conference-talk-transcript blog post! I wanted to share a little about the text editor I’ve been using, and gather a few things together that I wish I’d known when I picked it up.

Getting Started with Spacemacs: https://interblah.net/getting-started-with-spacemacs

#emacs #spacemacs #code #editors #vim #evil

@judofyr keen to see more of this!

@leoleo55 you can use the web, or Pinafore on web or mobile, or Amaroq, Tootdon, Toot.app - lots of possibilities!

@travis For me, the benefits of a super helpful git log and blame workflow vastly outweighs the challenges of coordinating rebasing feature branches.

And over time it encourages us to be more mindful of the commits we create in the first place, making them cleaning and more coherent from the outset.

@travis once it’s in master, complete agreed (and I think he says so in the talk).

For collaborative branches, a little work is required sure, but it’s hard to avoid unless you want to save all your merge conflicts to the end and have a bunch of “fix build” commits in there.

@dekkzz78 I can't think of anything super obvious; possibly some of the recent changes around the superclass of `Integer`, or the behaviour of `each` on `String` instances?

Lovely talk by @tekin about the benefits of investing time in keeping a clean and useful #git history, particularly the tips at the end.

https://vimeo.com/280579162

@brian_kephart I first used #Ruby as a language to control and glue together some C++ code I was writing to simulate insect construction behaviours

@mperham @sidekiq interesting idea. I do still like smaller contributions by individuals because hopefully that’ll give people a sense of ownership of their community, but if companies can afford more, that’d be great too

Don't worry @mperham, will stay 😄

(although you could be extra nice by becoming a super supporting anyway 😉 )

The Ruby.social Patreon now has a couple of benefits available for supporters:

Super supporters can now nominate a custom emoji which will be added to the instance for their (any anyone else's) use!

Companies/bigger organisations can now also show their support of Ruby.social with a logo and link from the homepage.

Find out more:

https://www.patreon.com/rubysocial