nyellin

Author of the original here. Thank you for the mention!

No, because every article will devolve into a discussion on if AI generated or not, and to what degree. Let content speak for itself.

OP here and the doctor was wonderful. If we fixed the interface they could help more patients in the same time.

It's a trade-off. In these scenarios we update our staging data for next time.

How does copy pasting an error into an LLM involve thinking?

I'm the OP and wanted to clarify. We do not give Claude Code access to production API keys. The intent was staging databases and I've updated the post to make it more clear.

We assume that every API key we put into Claude Code can be leaked and therefore make sure there's nothing sensitive behind them.

I'm the OP and this is the exact point of the post. Whoever handed you that project did not have Claude code running it end to end in a production-like environment.

Whether you like the vibe coded app or not, you would have had fewer errors if Claude had been testing it end to end while vibe coding.

As written elsewhere, we dont give access to prod! The DBs are staging and our assumption is that every key we give Claude will be leaked. I'll update the post to clarify

Fair enough, I will update

I'm the OP and to clarify we dont give access to prod DBs. The point is you need to give the LLM the ability to test end to end, and that can be done with staging data.

OP here: we don't give Claude Code access to prod. Everything is isolated cloud accounts for this purpose.

E.g. we give Claude credentials for db - but it's never prod data.

No, it was designed on paper by someone with no understanding of prompt caching and no consideration of latency or token costs

Why does Atlassian need to train AI models?