If your team just writes code, AI replaces it.
I help Rails teams own the product, not just the code: the developer workflows, the harness, and the agentic-coding patterns that make it real.
Your team is worth more when it owns the product, not the tickets.
When AI writes the code, the work that matters moves up. It moves to the people who decide what to build, shape how it feels, and stand behind it in production. A Rails team that only turns tickets into code is handing away the part AI can't do.
So the real goal is ownership. I help your developers work as product engineers, with AI carrying the implementation. The developer workflows, the AI harness around your coding agents, and the agentic-coding patterns that hold up in a real Rails codebase. This is a territory of expertise, not a packaged offer with tiers.
I think out loud about Ruby and AI, in the open, every week.
rubyonai
Writing and a weekly newsletter on AI-assisted Ruby and Rails. The thinking as it happens, while I'm still figuring it out, not a tidy retrospective after the fact.
read it rubyonai.com ↗ › in conversationWhere I work through the day to day of building this in public, with the engineers and founders building alongside me. Ongoing, not curated.
follow along /in/marostrowski ↗
I'm Marcin. I've been teaching this craft since 2015, and now I'm building it.
I founded fryga to build AI-powered Rails workflows. Before that I spent years as a Rails coach, then mentoring engineers at 42 Warsaw.
Teaching is still how I work. I learn a system properly by explaining it to someone else, and Ruby with AI is the system I'm explaining now. So when we talk, you get someone who has to make the ideas clear enough to teach, not just clever enough to demo.
When the work needs building, my team at fryga delivers. I do the thinking in public. We do the shipping in private. If a conversation turns into real work, you get a software house that has put AI into production Rails apps, not a solo consultant with a calendar.
Tell me about your team's AI adoption.
Where are your Rails developers getting stuck with Claude Code or Cursor? Book a call and we'll talk it through. No pitch, no deck.