ignurant

9 ms·

1.
by ignurant 11mo ago
For what it's worth, the last few years our we've sliced off a few custom client apps in Rails and it's felt like a great tailwind. We've been running a profitable BI app for around 15 years, but it's really hard to
2.
by ignurant 2y ago
A lot of people seem to overcomplicate it by bringing their thoughts on how other modern js apps are written. It would be helpful to have a specific example of some of the things you need to work through. Reading through the [handbook]( htt
3.
by ignurant 3y ago
Some of the most enlightening books I’ve read when I was first learning Ruby were Text Processing in Ruby, and Building Awesome Command Line Apps in Ruby 2. They each reveal certain features and perspectives that work towards this end, such
4.
by ignurant 3y ago
It is pretty cool. I’ve been using it for 3-4 years as a queue between Ruby and Node for scraping tasks. Ruby queues the work, a node worker does the downloading, and a Ruby process parses and loads data. It works incredibly well in my use
5.
by ignurant 3y ago
I think that's a great argument to consider when framing this concept to someone the first time. Avoid the `implicit return` language altogether. Instead focus on the expressions. `Implicit` triggers mental responses like "I prefe
6.
by ignurant 3y ago
I usually drink the DHH koolaide when it comes to Rails decisions, but I'm surprised by this decision exactly because of his arguments against being forced to write specific styles. I enjoyed default RuboCop when I was first learning R
7.
by ignurant 3y ago
I'm fluent in Ruby, and have nearly zero experience in the other languages featured in this article. The `implicit return` is often something people find rather willy-nilly when first learning Ruby. As such, I always thought that was a
8.
by ignurant 3y ago
I can appreciate that. There's a few revelations I've had over the years of learning Ruby that highlighted "why things are as they are". Decisions that feel arbitrary and against the grain, but actually make a lot of sen
9.
by ignurant 3y ago
I usually conditionally include the visibility toggle class from the erb side, so the first time it renders as html it has the toggle correctly initiated. I can see situations where the visibility logic is hard or impossible from the Ruby s
10.
by ignurant 3y ago
In addition to the Ruby under a Microscope (linked elsewhere), a lot of talks from Aaron Patterson (Tenderlove) are enlightening in this regard. I've learned a lot from them, and they also provided the inspiration to keep digging. Some
11.
by ignurant 3y ago
I would suggest that the Rails scene is at least worth checking out. I’ve seen a number of people move from .NET or Node to Ruby and Rails and thoroughly enjoy it, with little desire to go back. For reference, the last 12 years I’ve worked
12.
by ignurant 3y ago
> Is Rails still into magic? Yes, but you too [can join the magicians guild]( https://guides.rubyonrails.org/ ). They are very open. In fact, they even share with anyone [every single trick they know]( https://gi
13.
by ignurant 4y ago
New Rails 8 feature? (I’ll see myself out).
14.
by ignurant 5y ago
There’s even a book about that! https://datavisualizationtoolkit.com/ Who would have thought that the “Data Visualization Toolkit” would be about Rails? Turns out, it’s pretty sweet actually! rails new, g migration, baddabo