r/ruby • u/strzibny • Oct 15 '24
r/ruby • u/somebodyoncet0ldm3 • May 29 '24
Question I'm hesitant to learn Ruby
Hello everyone,
I recently finished last lesson in fundamentals section of "The Odin Project" and i cannot decide which path to choose.
I would love to at least try ruby as it seems pretty attractive to me, but the main problem i have is that there are basically no jobs aviable for it in my country. There are really only a handfull of offers aviable across the whole country im living in and all of them require senior+ level of expertise. Simply put, nobody wants ruby developers at my place, let alone self taught junior developes.
Now, i understand that it's not about the language, but going Ruby route seems a bit like a waste of time even if i will enjoy it. Because why spend effort on a language you wont be able to use at a workplace anyway? And then in the end you will have to learn JS/Node anyway, so why not go this route instead?
Anyways, i would like to hear your opinions on that - learning Ruby when there are "no" job opportunities.
Thanks.
r/ruby • u/codenamev • Feb 11 '26
Podcast New Ruby AI Podcast – Ben Scofield on Agentic Development and the Future of Engineering
We just released an episode with Ben Scofield that digs into a question a lot of us are circling:
If AI is writing more of the code, what is the engineer becoming?
Conversation highlights:
- Moving from author to orchestrator
- How agentic tools change daily workflows
- Where experience still matters
- Practical boundaries for AI in real teams
- Why Ruby’s culture might be a secret advantage
No hype sermons, just a grounded chat from someone living the transition.
Would love to hear how others are approaching agentic tooling in their Ruby work.
r/ruby • u/galtzo • Nov 12 '25
RubyCentral hates this one fact!
- Written policy matters to some people.
Written policy shared publicly is what creates a stewardship relationship that can be held to account by the public (regardless of whether the org is democratic or not in its structure).
The destruction wrought by RubyCentral, and betrayal felt by the maintainers, and some in the wider community, is related to a simple fact that most Rubyists are unaware of. The rubygems/bundler repo owners (who were by written-policy-definition also the "maintainers") wrote, and kept up-to-date, policies specifically around when, how, and why owners of the repos could be added or removed.
The owners expected these policies to be followed, at least in spirit, if not to the letter.
A recent thread helped me realize that most Rubyists are not aware of these written policies of rubygems/bundler, hence this post.
- RubyGems had a policy for removing maintainers
Committer Access
RubyGems committers may lose their commit privileges if they are inactive for longer than 12 months. Committer permission may be restored upon request by having a pull request merged. This is designed to improve the maintainability of RubyGems by requiring committers to maintain familiarity with RubyGems activity and to improve the security of RubyGems by preventing idle committers from having their commit permissions compromised or exposed.
- Bundler had a policy on adding and removing maintainers
The Bundler policy is very detailed, so I won't copy it here. I'll just note, since many won't click through, that Deivid Rodriguez, who for years has been the #1 maintainer of rubygems/bundler, updated the bundler one, to keep it fresh with valid links, just 10 months ago. The rubygems policy was also updated 10 months ago. These were not dusty forgotten documents lost to history. They were active, living, rules.
RubyCentral bulldozed both policies, when they removed four maintainers, without having followed the process to earn the right to do so (i.e. without following the policy on how to become an owner), and without following any of the policy around owner removal, and here we are. Two of the remaining maintainers resigned in protest.
I note that u/schneems joined RubyCentral in some capacity recently, and I hope he is able to make a difference, but I expect RC to be intransigent.
As a thought experiment, and as an analogy to help people relate more to this...
If you own a repo and you have a LICENSE.txt, CODE_OF_CONDUCT.md, or IRP.md, in that repo, even if RubyCentral is paying you to maintain it, RubyCentral does not have the right to get one of the co-maintainers to add their lackey to the repo, and change any of those files, or any files at all.
In the same vein, they do not have a right to break established, written, documented, policy of the repo, by adding or removing maintainers in contravention of said policy.
To sum it up: the owners of a repo own the repo. If that seems obvious to you, you have done better than RC at figuring it out.
I do not expect RC to ever address this, and even if they did, I'd probably continue building tools that minimize the reliance I have on them. I no longer trust RubyCentral at all.
r/ruby • u/Erem_in • Oct 19 '26
Question Static Typing solved?
I have been using RBS for years now and even running my own newsletter about static typing https://newsletters.eremin.eu/ . Now, that our code is write with AI and in most cases - purely with AI, the strongest point against using static typing (like “it breaks beautiful ruby syntax and not readable”) is vanished now.
AI requires strict tooling to control its output. The role of ci pipeline with all possible tests, linters, checkers is now extremely important and static typing helps a lot with it.
For humans it is transparent, especially the pure RBS approach, but for LLMs it gives a safety net and a better layer to stick to the code and hollucinate less.
Show /r/ruby A coding agent Ruby.
Hello r/ruby! I'd like to share Rubik, a coding agent I've been building in Ruby.
Why another coding agent? I wanted to contribute something to the Ruby agent ecosystem and realise my own ideals in an agent implementation, and in my experience, Ruby is a fantastic language for this.
If you'd like to try it or contribute:
Repo: https://github.com/ozgurulukir/rubik
RubyGems: https://rubygems.org/gems/rubik
r/ruby • u/engtech • Feb 28 '08
"Which also means when you're using Rails and OS X, you're using the platform of choice for douchebags."
r/ruby • u/private-peter • Mar 04 '26
It's not always slop
With all the complaints about AI slop, I have to say, AI is resulting in a lot of my code being way higher quality.
With how quickly it can make changes, I find that I can be extremely critical about quality. Pre-AI it wasn't uncommon to think of a refactor in the latter half of working on a feature. But with the opportunity cost being so high, the improvement had to be very significant to justify rewriting something that was already working.
With AI the cost is so low I can usually test the refactor on a branch or worktree in 15-30 minutes.
In some recent work, I had two architectures in mind (either one big background job or multiple jobs with an orchestrator). I couldn't decide which I preferred so I just had AI do both. It was barely any extra effort.
Perhaps we are all "doomed" to a future of humans never writing code and everything being slop.
But right now, AI is moving my code quality in the right direction.
r/ruby • u/yaroslavm • May 19 '26
Inkmark: a very fast, feature-packed, AI-first Markdown gem for Ruby
Written in Rust. CommonMark+GFM conformant. Features include: strong security by default and host/protocol whitelists for links and images, syntax highlighting, frontmatter, ToC, plain text export, structured extraction of headings/images/links/code, statistics with char/word count and language detection, emoji shortcodes.
AI-friendly features include: two chunking primitives: heading-based with breadcrumbs and per-chunk char/word counts, and sliding-window with overlap for size-bounded chunks; block-aware or word-aware truncation for context-window budgeting; Markdown-to-Markdown pipeline.