Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

i love this because it seems like you've turned vibecoding up to 11 unleashing the non-technicals in your org to ship vibecode slop straight to prod. it's an idea so obviously terrible to most engineers that maybe it's actually really really smart. much bolder than yet another AI-driven dashboarding tool or smart notebook.

to address the elephant in the room... how do you think about technical debt incurred by users who likely do not understand the underlying data models, consider auth, etc?



Exactly ;) One of our customers say "we've given their entire team superpowers"

I've been dealing with technical debt for half of my career. Here's what we're doing to prevent it:

- We don't ship to prod or to the main repo -- each feature is a scoped, sandboxed, separately version controlled "app".

- We have a proxy layer to pin API versions, so if the underlying contracts change, we still support all past created apps.

- Authentication follows your SaaS platform's RBAC and authentication tokens, making it easy to share within a team or across multiple tenants.


Not the op but I think of it as “job security” for developers when they’re called to fix.




Consider applying for YC's Fall 2026 batch! Applications are open till July 27.

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: