Ruby can be used for different purposes. Web development is likely the most popular choice, but there are other options like:
Share with the community how you’re currently using it, feel free to share as many details as you’re comfortable with.
In my job, it’s obvious but it’s by Rails framework.
As for personal stuff, I like creating scripts or CLIs with it. 
Mostly Rails apps and rake tasks to do the dirty work in production 
My work partner and I have written, maintain, and administrate 68 rails applications, along with 18 private supporting gems to support scientific research and its administration. Publicly, try to help out with the activerecord-oracle_enhanced-adapter and geminabox gems.
I also write and slew of command-line tools to help administrate the apps, my system, and accelerate my programming, and automate background tasks of all sorts (monitoring, and summaries, and static analysis).
Indirectly one of my personal projects plays into my work too, because I use the bujo-pdf to do work related planning on my ipad, so I’m including it, also because I think it is a fun use of prawn.
Its not the only language in play, but it is my favorite.
I’m currently working on a Ruby on Rails project that uses micro-services in Rails and Go. So it’s mostly exposing API’s that perform business functions using background jobs and read/save from the database.
@juanvqz What gems do you use to generate CLI tools?
@guim What kind of dirty production work? Is it automation, migrations, and that kind of stuff?
@andynu I didn’t know about geminabox. It’s cool it can serve as a proxy too. bujo-pdf looks great too! The calendar views can be very helpful for planning, although I’ll probably print them instead, since I don’t have an iPad.
That’s basically it, some automations.
Many errors occur due to technical issues, so we create some rake tasks and run them in Jenkins, since we don’t have direct access to the production machine to use the rails console and all of that.
@javier.cervantes For me, to make a good CLI experience and not reinvent the wheel, using the gems from here https://ttytoolkit.org is a must.
I’ll take a look at TTY! Do you publish your CLIs somewhere or they’re mostly for your own workflows?
Not really, I only published this one:
I wanted to build in public and was useful for me because will help tracking my time from the terminal.
But after I became a Raycast user, I ended up creating an extension for the same purpose: GitHub - JuanVqz/noko-for-raycast · GitHub
Raycast is basically Apple’s Spotlight, but with steroids.
I’ve done a lot of client work building Rails applications end to end, and I am often the sole maintainer on those systems, working directly with the business owners.
I also work within teams as a consultant/advisor on much bigger Rails apps that deal with the various problems that come w. growth and scale, so I get to see what that looks like without having to be responsible for those systems myself, and I kind of prefer it that way.
But these days, I’ve also been working on building rapid prototyping tools, and that perhaps surprisingly has sent me down the path of stripping away layers to be able to do more low-level framework building. I’ve very much been enjoying that process, playing around with some ideas directly at the Rack level, and building out my own set of tools using nothing but hanami-router on top of Rack.
I recommend giving that a try if you’ve not done it before. It’s a very quick way of seeing how much Rails is doing for you, but also to see how much the foundational layers are not magic, and are even a lot more approachable than they might seem on the surface.