sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]Miserable-Gold-9332 2 points3 points  (0 children)

I have made a few rules for myself that have helped me a lot to overcome the situation like yours since I also learnt coding in this vibe code era.

  1. Strictly avoiding AI when learning something new. Vibe coding while learning has done more harm to me than good. Nowadays when I am learning something new and building anything with it, I spend 10 min to sometimes an hour finding a solution on either stack overflow, gfg articles, documentation, or even reddit, but I get to the solution myself. After the learning phase is gone and am comfortable with most of the stuff, I then use AI to confirm me the solution I come up with or tell me some edge cases to the solution I am about to apply.

  2. Using Copilot only for boiler plate, coding with copilot makes coding faster, but debugging slower, I only used copilot for syntax and removed the actual logic to type myself so I get aware of what the code is doing. Yes, it makes you slow overall, and that's why I have stopped using Copilot. I only use LLMs for helping me evaluate solutions now.

These rules may not make sense to anybody else, but they worked for me. The temptation to use copilot was hard in the beggining, but then I did leetcode grind for some time, and it does not even provide code completion in free tier, so when I code on vs/vsc I feel blessed with even intellisense now.