Show HN: Sheet Ninja – Google Sheets as a CRUD Back End for Vibe Coders
41–50 of 83 posts
Re: Show HN: Sheet Ninja – Google Sheets as a CRUD Back End for Vibe Coders
#42I put Google Sheets as a backend (in production) when i wanted a select non technical people to be able to see and modify the data without the cost of building a backend. I really wish auth was easier to setup for services though, i see no reason google can't provide this out of the box
Re: Show HN: Sheet Ninja – Google Sheets as a CRUD Back End for Vibe Coders
#43I have done this for my own projects for years it’s great for projects that are only for me and gives me a very good db editor also. Cool project though the only risk I see is that if the target audience are vibe coders they will you known just vibe code an integration
We're thinking of playing around with the pricing right now to make sure it is cheaper to just use this than to spend the time and tokens recreating the logic. We will see how it plays out.
Re: Show HN: Sheet Ninja – Google Sheets as a CRUD Back End for Vibe Coders
#44Earlier quoted context omitted.
Cloud sql lowest tier is pennies a day, this ninja platform is also not free. A spreadsheet is a misclick away from corruption, why not spend another prompt on getting Claude to configure a db?
Which works out at $100 USD / year. You might think that's trivial, but when you start provisioning multiple environments over multiple projects it starts to add up. It's a shame that Google haven't managed to come up with a scale to zero option or serverless alternative that's compatible.
But what would scare me the most, is that google can easily shut this thing down.
Re: Show HN: Sheet Ninja – Google Sheets as a CRUD Back End for Vibe Coders
#45I put Google Sheets as a backend (in production) when i wanted a select non technical people to be able to see and modify the data without the cost of building a backend. I really wish auth was easier to setup for services though, i see no reason google can't provide this out of the box
You can auth with Google auth after you configure an app, what are you thinking of that would be simpler?
Re: Show HN: Sheet Ninja – Google Sheets as a CRUD Back End for Vibe Coders
#46Earlier quoted context omitted.
You can auth with Google auth after you configure an app, what are you thinking of that would be simpler?
I meant to authenticate a service (that is not running on GCP) to access the sheet, it requires a service account and felt more convoluted than what it needs to be
Re: Show HN: Sheet Ninja – Google Sheets as a CRUD Back End for Vibe Coders
#47SQLite, SQLite + drizzle with WAL mode, push it to a VPS, do not waste your time on anything else :) Thank me when things become super easy! When things scale, SQLite will still be fine, will fit 99% of the vibe coders needs! When they don't then migrate to what ever!
This requires technical skill
Re: Show HN: Sheet Ninja – Google Sheets as a CRUD Back End for Vibe Coders
#48Don’t really get the purpose for this apart from throw away projects. For vibe coders is it really “hours” setting up a database these days? GCP cloud sql + drizzle ORM is minutes and actually scales unlike a spreadsheet, heck Claude can even write you a deployment script and run it over GCP CLI.
Cloud SQL costs gazillions, sheet is free (other than selling your data)
Re: Show HN: Sheet Ninja – Google Sheets as a CRUD Back End for Vibe Coders
#49Re: Show HN: Sheet Ninja – Google Sheets as a CRUD Back End for Vibe Coders
#50Hi all - a friend and I have been dabbling in the entrepreneur space for years, but we never really pulled the trigger because of our corporate jobs. We suffer from the same thing that plagues a lot of engineers: we know how to build products, but we are weak at distribution and marketing. We feel that being able to build is becoming table stakes and the ability to actually get a product into people's hands is more i…
One thing I've noticed from the sheets-as-backend pattern: the reason people keep reaching for spreadsheets is because the editing UX is instant and familiar.Any tool that wants to replace this for non-technical users needs to nail that "just click a cell and type" experience. That's the hard part honestly.