Skip to main content

Command Palette

Search for a command to run...

Building admin panels sucks ๐Ÿ˜ก

Updated
โ€ข2 min read

I've probably built a hundred of them in the past, and I was mostly doing a bad job.

I started seeing similarities from one to another. Common features which, even if they seemed simple to build, I would still make the same mistakes over and over again. It sounds like I have a memory problem or I'm a bad engineer but when I spoke with other developers, they happened to do the same and it wasn't just me

The next thing I did was try to extract tiny bits that I could re-use in multiple projects. That worked out nicely for a while but I ended up with fragmented bits of code that were brittle when put together and had slight variations from project to project.

That's when it hit me ๐Ÿคฏ

Internal tools should be built in a cohesive framework that is purposely made for that. We do the same with E-commerce, with Content Management Systems, with Application Tracking Systems, and other pieces of software. We have platforms purposefully built for a specific job.

So why should we cobble together odd libraries, spend precious time, focus, and resources to build the same thing that we built over and over again. We should use those resources to focus on the things that make our app bring that unique value to our customers.

So, Avo was born out of necessity - the framework that makes building internal tools a breeze

If any of this resonated with you, go to https://avo.cool (yes, that's a valid domain name) and give it a try.

More from this blog

Own it - A blog from Adrian Marin

23 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