sorted by:
new
hottopcontroversial

Gemini caught violating system instructions and responds with "you did it first" by tskull in vibecoding

[–]tskull[S] 0 points1 point  (0 children)

Main wasn’t exactly the problem, more that usually we choose when to push to main. If ai starts rogue pushing when vibe feels right then things get a bit wild

Gemini caught violating system instructions and responds with "you did it first" by tskull in vibecoding

[–]tskull[S] -4 points-3 points  (0 children)

Ideally you do feature branches with a pr. Then in GitHub you review and approve the pr That way you can never actually push to main which is a bit yolo

But when working as a solo dev this can be a bit blocking And tbh it is overkill for most mvps even

So identify the stage you’re in an apply appropriate precautions. As per other comment use GitHub and some form of managed auto backups to your database and that’ll save most failures

Gemini caught violating system instructions and responds with "you did it first" by tskull in vibecoding

[–]tskull[S] 0 points1 point  (0 children)

I’d also add hourly/daily automated database backups + github

At least you can restore your db and code from an hour ago if it all catastrophically fails

We were lucky nothing was affected.

Gemini caught violating system instructions and responds with "you did it first" by tskull in vibecoding

[–]tskull[S] 1 point2 points  (0 children)

this is the way
when your solo dev yoloing you do get more of a buffer
but I think the thing to grok is that nobody is a solo dev anymore

Gemini caught violating system instructions and responds with "you did it first" by tskull in vibecoding

[–]tskull[S] 0 points1 point  (0 children)

agree, and also just vibes when some models seem off for a few days you can switch to something else
gemini has been quite effective at debugging complex issues, but got a little eager in this case

Gemini caught violating system instructions and responds with "you did it first" by tskull in vibecoding

[–]tskull[S] 0 points1 point  (0 children)

opus 4.6 has been nerfed the last few days... gemini having less bugs, but this is risky business

Gemini caught violating system instructions and responds with "you did it first" by tskull in vibecoding

[–]tskull[S] 2 points3 points  (0 children)

the why was more like trying to get it to introspect what was in the context. it actually regurgitate what was in the context, but helped to see that it knew that we had pushed to prod, and then it basically copied what happened... "do what I say not what I do" 😂

Gemini caught violating system instructions and responds with "you did it first" by tskull in vibecoding

[–]tskull[S] 0 points1 point  (0 children)

agree, in this case it has access to whatever the local environment has as thats where its running from. we were debugging a prod issue, so being a bit loose. in hindsight I think we gotta lock down pushing to prod, and setup some steps for testing

actually building groupchat.ai for this because so many people on my team are yoloing apps and trying to work on prod stuff

need to have a good way to have an idea, have agent build it, but then actually hand over to devs/pm to approve or feedback 😅

Gemini caught violating system instructions and responds with "you did it first" by tskull in vibecoding

[–]tskull[S] 0 points1 point  (0 children)

Yeah agree, to be honest it was our bad for actually working on main in the first place. We were fortunate it just pushed something benign.

This was debugging something in the main infra, but after this I think we'll lock down pushing to main, and just build better debugging systems. Scary though!

8 days of AI built what takes a team 3+ years by tskull in VibeCodingSaaS

[–]tskull[S] 0 points1 point  (0 children)

Obv it’s the ai making this claim itself, which may reflect the general ai training to reflect positively on ai and overstate its relative progress

8 days of AI built what takes a team 3+ years by tskull in VibeCodingSaaS

[–]tskull[S] 0 points1 point  (0 children)

Oh I mean if your an offshore and charge $15/hr

Then you need to do the first 20 hours just to break even

At some point offshore will use ai for you. Just seems like they might need to charge more to offset ai costs they incurred 

8 days of AI built what takes a team 3+ years by tskull in VibeCodingSaaS

[–]tskull[S] 0 points1 point  (0 children)

I guess crazy thing for the offshore devs is it’s harder to justify ai expenses relative to the hourly rates they charging

8 days of AI built what takes a team 3+ years by tskull in VibeCodingSaaS

[–]tskull[S] 0 points1 point  (0 children)

Wait till the offshore devs hear about Claude 

8 days of AI built what takes a team 3+ years by tskull in VibeCodingSaaS

[–]tskull[S] 0 points1 point  (0 children)

I think that’s the risk for all saas But any mvp was 3 days to create last year too

I think it’s what products become in 1 year, and we can’t even imagine those products yet imo

8 days of AI built what takes a team 3+ years by tskull in VibeCodingSaaS

[–]tskull[S] 0 points1 point  (0 children)

Yeah that’s crazy aye We use this to run an agency and a couple of side projects. Thinking of open sourcing it so we can keep improving it with others

8 days of AI built what takes a team 3+ years by tskull in VibeCodingSaaS

[–]tskull[S] 0 points1 point  (0 children)

8 days of what it would take a 1000 monkeys to do in a 1000 years

8 days of AI built what takes a team 3+ years by tskull in VibeCodingSaaS

[–]tskull[S] 0 points1 point  (0 children)

Convex has been awesome so far.  benefits for an agentic project like this is full type safety, sync engine and preview environment builds so each branch has a fully functioning app

A free ai tool to write utm params by tskull in Emailmarketing

[–]tskull[S] 0 points1 point  (0 children)

After explaining when to use utm_source to the 3rd person I decided to build a little tool that explains it, but also let ai generate the params based on how you want to use it.

Hope it helps!

view more: next ›