Your company's digital brain
I'ma self-taught developer on my journey to become a successful indie dev.
For more content follow me on Twitter @adrianthedev
Search for a command to run...
I'ma self-taught developer on my journey to become a successful indie dev.
For more content follow me on Twitter @adrianthedev
No comments yet. Be the first to comment.
I want to share my experience regarding AI-driven development.I know it's not a new and shiny thing, and it's been around for a while now, but some things should need some time to take it through its

I think it's important that the Ruby community knows what just happened in San Francisco last week. 400+ Rubyists got together and shared ideas and visions. They exchanged opinions and presented the past, present, and future of Ruby. I went to very ...

Tl;DR; We're taking a break with Friendly.rb. We had three beautiful editions, incredible fun, and learned so much in the process. This happening changed us, the hosts in ways we could not imagine. We're taking a break because things have happened in...

Here's something that's been on my mind lately about the Rails ecosystem. For the past 10 years, there's been massive investment in dev tooling, especially for JavaScript and TypeScript companies. They take some of that funding and deploy it to marke...
Own it - A blog from Adrian Marin
24 posts
Sharing my lessons on becoming a thriving #indiedev.
๐ Launching Avo into the world! - ๐ฅ A beautiful, easy-to-use Ruby on Rails admin panel framework
What do you need in your digital brain?
That's how I think about Avo now. It's not some closeted admin panel where only five people dare to go because touching the data wrong might crash the app.
It's the place where you invite your whole team to run your operations. Managing plans, subscriptions, users, everything that keeps your business running.
The problem we're solving is the same one Rails solved years ago: stop building the same thing over and over again. Rails doesn't make you build your own view layer, modeling, or database layer because that groundwork is already there, battle-tested by hundreds of thousands of apps.
Same with Avo. We have hundreds of customers running this in production. They've kicked the tires, hit edge cases, found corner cases. We've fixed them. So when you need to build operational software, internal tools, or content management systems, you get all that knowledge baked in.
You'll probably have most of the features you need before you actually need them.
That's the power of building on proven foundations instead of reinventing the wheel every time.
What operational tools are you still building from scratch that you wish someone had already solved?