elsat on Nostr: Everyone has an opinion on vibe coding. Here is my experience a few months in: ...

Everyone has an opinion on vibe coding.

Here is my experience a few months in:


-produced unreviewable code
-fixed dozens of bugs
-shipped code now in production
-analyzed crash reports for common patterns
-made multiple prototypes quickly
-annoyed devs with PRs
-produced and tested with tens of files a working nostr app with a team of vibe coders in 24 hours that is better than most nostr apps
-found interoperability bugs
-found privacy leaks
-found security vulnerabilities
-found issues, gaps in deep technical libraries
-learned what commits, rebasing are by doing
-built a working zero-copy video player SDK
-upgraded SDKs with bugfixes, CI, or feature upgrades
-built a crash reporting prototype
-built a nostr native push notification implementation for Android
-built a integrated wallet prototype
-a bunch more stuff
-much of will never get merged
-a bit which I hope will be useful to devs and their customers

I’m still learning how to better work with devs.

I now understand stuff I never could have about software engineering when I just wore a product hat.

It’s not a replacement for the devs on the things worked on already.

I became a code contributor.

I’ve gotten my dev teams to embrace and tinker with agents.

A lot more is possible now without having the resources to hire more devs.

I aim to better serve devs and customers, and am better equipped to do so now.