← Back to context

Comment by sudo-i

3 days ago

The problem is that code as a 1-off is excellent, but as a maintainable piece of code that needs to be in source control, shared across teams, follow standard SLDC, be immutable, and track changes in some state - it's just not there.

If an intern handed me code like this to deploy an EC2 instance in production, I would need to have a long discussion about their decisions.

How do you know without seeing the code?

How do you know the criteria you mention hasn't (or can't) be factored into any prompt and context tuning?

How do you know that all the criteria that was important in the pre-llm world still has the same priority as their capabilities increase?

How do you know? Have you seen the code GP generated?

  • No, have you? They always seem to be missing from these types of posts. Personally I am skeptical, as AI has been abysmal at 1 shot provisioning actual quality cloud infrastructure. I wish it could, because it would make my life a lot less annoying. Unfortunately I have yet to really see it.

I'd love to hear how grok works inside agentic coders like cursor or copilot for production code bases.