Earlier quoted context omitted.
If you have to tell others that then perhaps some introspection for yourself might be helpful. Comes across more as denial than constructive commentary. I do believe the benefit decreases the more senior or familiar the work is but there is still a noticeable benefit and I think it largely depends on the velocity and life cycle of the product. I think you get less benefit the slower the velocity or the more mature of…
Again, show your evidence. You make a polite but still ad hominem "attack" about me instead of addressing my points with demonstrations of evidence. Make a video or blog article actually showing how your use of LLMs in coding is making you more productive. Show what it's doing to help you that has a multiplier effect on your productivity.
I don't think it deserves a video or blog, like I already said the multiple posts that have made HN front page have covered it well. - Autocomplete saves me keystrokes usually - Features like Cursor's composer/agent allow me to outsource junior level changes to the code base. I can copy/paste my requirements and it gives me the diffs of the changes when its done. Its often at a junior level or better and tackles multi-file changes. I usually kick this off and go make other changes to the code base.
Now like I have said before, this depends a lot on the velocity of the team and the maturity of the code base. I think more mature products you will have less benefit on feature implementation and most likely more opportunity in the test writing capabilities. Likewise, teams with a slower cadence, thinking a bluechip software company compared to a startup, are not going to get as much benefit either.
Instead of being so aggressive, simply say why it does not work for you. These tools strive in web dev which you may not be involved in!