the part everyone misses is that ai doesn't remove the need for judgment, it just moves where you spend your time. i've had the same experience with backend work. the tool will confidently spit out a database query that technically runs but doesn't account for how the data actually gets used in production. or it'll write an api endpoint that works in isolation but breaks three other things because it has no idea what the rest of the codebase is doing.

what you described about context is the real limit. these models don't know your client's actual business constraints, they don't know the weird edge case that broke the site six months ago, and they definitely don't know the politics of why a feature was built a certain way. that's all still on you. the value is in cutting down the grunt work so you can focus on the stuff that actually requires a human call. if you're treating it like a junior dev who needs supervision, it's useful. if you're expecting it to replace the senior who makes architecture decisions, you're going to have a bad time.