Explore tweets tagged as #rubyforall
Hey @CelsoDeSa, I just wanted to say thanks for the fantastic insights you shared on @rubyforall. Your advice on interviews, ADHD and time management was inspiring. I would love to ask you a few questions about Ruby and Rails in the future. Apologies for DMs being closed!
1
0
2
1
0
3
@andrewmcodes @rubyforall GoodJob has quickly became my favourite gem in the last year. It is a packed with features & easier to deploy. https://t.co/UBehPZEoc3
3
0
14
2
0
12
@cm_richards @andrewmcodes @rubyforall @bensheldon I think project’s README has a great comparison table for different background job gems. You should check it out.
0
0
1
0
0
0
@andrewmcodes @rubyforall ActiveSupport. 3.days.ago remains an absolute fucking joy.
1
0
0
@andrewmcodes @rubyforall The cheekiness of it: "Enterprisey Apps Invite, Nay Demand, Enterprisey Rates. Verily, Sunshine." - in a time when people were complaining that rails couldn't scale they showed up and said... nah, we gotta slow it down to make it feel real.
0
0
0
@rubyforall This one was tricky. https://t.co/xEuPxNOeoo
Took a full day to figure out an error today in production Rails App 👇 "WebSocket error occurred: wrong number of arguments (given 2, expected 1)" Issue description and how I resolved it 🧵
1
0
2
Yo @JasonSwett. Any chance the talks for this years Sin City Ruby were recorded? Been listening to the latest episode of @rubyforall where they’re going over the talks and I’m having some serious FOMO. 😅
1
0
0
@andrewmcodes @rubyforall only if you're ready to take your poros to the next level
2
0
11
@rubyforall Pure OO in Ruby ------------------ You see: 1 + 1 #=> 2 But really here's what's really going on: 1.+(1) #=> 2 1 receives the message "+" with an argument of 1 and returns 2.
1
0
3
1
0
1
@andrewmcodes @rubyforall @andatki mmmm databases. Btw that MySQL string truncation problem you discussed. Normally the insert would be rejected for being too long. Sounds like on that specific DB someone disabled strict mode :).
1
0
3
@rubyforall It didn't take a lot of time to figure this out but this was also a tricky one. https://t.co/zVjNh8RZHr
API only Rails app was suddenly throwing CORS error in Frontend. It was working perfectly an hour ago and I couldn't remember what I had changed. Turned out to be Nginx Passenger issue, it was pointing to wrong Ruby version. Sometimes error is not where you think it is.
1
0
2
@andrewmcodes @rubyforall Second place is the `t` gem. Because I've used it so so much for so many years. h/t @sferik
1
0
2