Comment by mariogintili

> What’s funny is that many companies hiring “AI engineers” don’t really know what they’re doing. I’ve had interviews where they openly said: “We don’t really have AI expertise, but we know we need AI.” That’s how things are right now. It’s both good and bad. They can’t really judge your skills properly — but that also means your chances of passing are higher.

A lot of money is being thrown around at AI, it's a good time to open a company :) I agree.

> As for the Ruby/Rails world — I’m honestly very disappointed. The market feels completely saturated. There are too many experienced engineers competing for too few roles. Being good is no longer enough.

Ruby/Rails, and other platforms NEED deep AI integration. That wave is coming.

I am surprised that people don't do a rails new for their new startups. I still see it as the king of web frameworks.

> With LLMs, the world changed. You take the best tools available. Next.js with standardized React components instead of Stimulus and Turbo. Hosted auth instead of rolling your own. When I needed to integrate something like Clerk, I just dropped in a component and moved on. There are tons of ready-made solutions in the React ecosystem.

Show me those ready made solutions? I haven't used them commercially so I can't vouch for them

> Now compare that to Ruby. Are there modern AI libraries? Yes, technically. Are they well-maintained? Not really. You’re often dealing with abandonware. LangChain officially supports Python and TypeScript — not Ruby. And like it or not, AI today is happening in Python.

True, I should probably ship something in Python and just add that to my inventory.

> The more time you spend clinging to Ruby/Rails, the further behind you get. That’s just reality. My advice is simple: if you can, move on. The opportunity window in AI is wide open right now, but it won’t stay that way forever. 2026 is probably the last really good entry point.

I agree with you! time to move to new pastures