Remember though that lazyness, as I learned in computing, is kinda "doing something later": you might have pushed the change/fix faster than your senior fellow programmer, but you still need to review and test that change right? Maybe the change you're talking about was really trivial and you just needed to refresh your browser to see a trivial change, but when it's not, being lazy about a change will only gets you suffer more when reviewing a pr and testing the non trivial change working for thousands customers with different devices
The problem is he wasn't comfortable with my solution even though it was clearly faster and it could be tested instantly. It's a mental block for him and a lot of people in this industry.
I don't advocate blindly trusting LLMs. I don't either and of course test whatever it spits out.
Testing usually isn’t enough if you don’t understand the solution in the first place. Testing is a sanity check for a solution that you do understand. Testing can’t prove correctness, it can only rind (some) errors.
LLMs are fine for inspiration in developing a solution.
