James Adam boosted

@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.

@esparta sorry to hear that you're still having issues, but glad it's not something wrong with ruby.social itself! @mastohost -- any ideas?

@esparta if you’re able to try it either with a different browser and/or not Tor that’s certainly help debug it…

James Adam boosted

Want to experience the lemurs and learn Ruby like you've never learned it before? My talk, "Reducing Enumerable - An Illustrated Adventure", is now live!

Learn about reduce and functional programming from a merry band of cartoon lemurs.

youtube.com/watch?v=x3b9KlzjJN

@esparta shouldn’t be a restriction. Is the problem still happening for you?

@dekkzz78 it looks like ActivityPub compatibility for Friendica is relatively new (friendi.ca/2018/11/18/activity) -- could that be part of the issue?

I don't think there's anything specific about ruby.social that's different from any other Mastodon instance; perhaps it's related to the Mastodon version though? This is currently running Mastodon 2.6.1.

@dekkzz78 there's been no specific configuration about that, so if friendica and mastodon are normally able to syndicate, then it should work with ruby.social.

Are you seeing problems?

@hankg we've had our ups and downs, but it's been very rewarding overall. Looking forward to the next ten!

Ten years ago, I sat around a fire with some friends after a disappointing big-budget conference, and decided to see if we could do something different. From that seed grew Ruby Manor -- can't believe we've been doing it for a decade!

rubymanor.org/#when

twitter.com/rubymanor/status/1

@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?

James Adam boosted

via the birdsite, avdi is giving away free 1 year subscriptions to ruby tapas to interested female devs twitter.com/avdi/status/104570

James Adam boosted

has anyone used GraphQL with a Ruby backend? how was the experience?

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: interblah.net/getting-started-

James Adam boosted

so I've been playing with composable validations

@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.

Show more
Ruby.social

A Mastodon instance for Rubyists & friends