---
title: "Comment by Muhammad Saqib on \"When AI-Written Code Becomes the Death of Deep Understanding\" | Hashnode"
description: "I really relate to this. I built my HintWordly website using Cursor AI—even though I’m a DevOps engineer and comfortable with AWS architecture and deployment. G"
url: "https://hashnode.com/posts/the-vibe-review-trap-when-ai-written-code-becomes-the-death-of-deep-understanding/69f59df8ec32cba9e5be818a/comment/69f708b40ab374db9994df68"
---

[Discussion](https://hashnode.com/posts/the-vibe-review-trap-when-ai-written-code-becomes-the-death-of-deep-understanding/69f59df8ec32cba9e5be818a)

Comment [When AI-Written Code Becomes the Death of Deep Understanding](https://hashnode.com/posts/the-vibe-review-trap-when-ai-written-code-becomes-the-death-of-deep-understanding/69f59df8ec32cba9e5be818a)

[Muhammad Saqib](https://hashnode.com/@saqib1993)

[May 3](https://hashnode.com/posts/the-vibe-review-trap-when-ai-written-code-becomes-the-death-of-deep-understanding/69f59df8ec32cba9e5be818a/comment/69f708b40ab374db9994df68)

I really relate to this. I built my [HintWordly](https://yourwebsite.com/) website using Cursor AI—even though I’m a DevOps engineer and comfortable with AWS architecture and deployment. Getting the system live was smooth, but now I’m hitting a wall with code optimization.

Since most of the code was AI-generated, I didn’t build the logic layer by layer myself. Now I struggle with things like reducing redundant API calls, improving query efficiency, and refactoring components to avoid unnecessary re-renders. Even tracing performance bottlenecks (like high response time or memory usage) takes more effort because I’m not fully familiar with every part of the codebase. like in that way?

It really shows that while AI helps you build fast, optimizing and scaling the code still requires deep understanding of how everything works underneath.

[Hasitha Wickramasinghe](https://hashnode.com/@haZya)

[May 3](https://hashnode.com/posts/the-vibe-review-trap-when-ai-written-code-becomes-the-death-of-deep-understanding/69f59df8ec32cba9e5be818a/comment/69f708b40ab374db9994df68#reply-69f7cc4976c1469ba4fb33fb)

I really appreciate you sharing this. First off, congrats on getting HintWordly live! As a DevOps engineer, you’re probably used to seeing the "big picture" of architecture, so it must be really frustrating when the "micro-logic" of the code feels like a black box.

This is the "hidden tax" of AI code. We save time upfront but pay it back with interest during debugging. It really reinforces the concern that I wanted to capture in this opinion piece, that is, the "ownership gap".

This quote I heard from Andrej Karpathy perfectly described it: "We can outsource the thinking, but we can't outsource the understanding". Scaling and optimization are where the "vibe" ends and engineering begins. Thanks for reading and sharing such a relatable struggle, and best of luck with the refactoring!
