Vibe codingHardvc-g360

Subject Ai code reviewLevel Senior–Staff~18 minCommon in Algorithms & data structures interviewsIndustries Computer games, Software development

Question

An AI assistant wrote this per-frame material update for an OpenGL renderer in C++. Visually it's correct, but the profiler shows a multi-millisecond CPU stall every frame and GPU occupancy is low. Review the render loop and explain why updating the uniform this way stalls the pipeline.

cpp

1void Renderer::DrawObjects(float time) {2    for (auto& obj : objects) {3        glUseProgram(obj.shader);4        GLint loc = glGetUniformLocation(obj.shader, "uTime"); // every object, every frame5        glUniform1f(loc, time);6        glUniformMatrix4fv(modelLoc, 1, GL_FALSE, &obj.model[0][0]);7        obj.material->Bind();      // re-uploads full texture set8        glDrawElements(GL_TRIANGLES, obj.indexCount, GL_UNSIGNED_INT, 0);9    }10}

What a strong answer looks like

Treat the AI’s output as a draft to verify, not an answer to trust. Name the specific flaw and the input that triggers it, say how you’d catch it — tests, edge cases, reading critically — and how you’d re-prompt or decompose to get it right.

Learn the concepts

Describe your solution

Vibe coding: describe the solution in plain language (or narrate it) and the coach grades your approach. Generating runnable code from your description is coming next.

Run or narrate your approach, then ask the coach.