AI Lazyslop and Personal Responsibility
danielsada.tech
AI Lazyslop and Personal Responsibility
1–10 of 75 posts
Re: AI Lazyslop and Personal Responsibility
#2If you get a 1600 line PR you just close it and ask them to break it up into reviewable chunks. If your workplace has an issue with that, quit. This was true before AI and will be true after AI.
Re: AI Lazyslop and Personal Responsibility
#3> Then, I’d get a ping from his manager asking on why am I blocking the review.
If you are in a culture like this, you may as well just ship slop.
Management wants to break stuff, that is on them.
Re: AI Lazyslop and Personal Responsibility
#4At the end there's a typo "catched" should be caught.
Otherwise, agree-ish. There should be business practices in place for responsible AI use to avoid coworkers having to suffer from bad usage.
Re: AI Lazyslop and Personal Responsibility
#5> Then, I’d get a ping from his manager asking on why am I blocking the review. If you are in a culture like this, you may as well just ship slop. Management wants to break stuff, that is on them.
Right, I think there is always a balance between being strict on code reviews, and just letting people ship stuff. I've also seen the other end of the stick in which a senior employee is blocking an important pr over "spacing".
Re: AI Lazyslop and Personal Responsibility
#6At the end there's a typo "catched" should be caught. Otherwise, agree-ish. There should be business practices in place for responsible AI use to avoid coworkers having to suffer from bad usage.
Thanks! Fixed.
Re: AI Lazyslop and Personal Responsibility
#7> Then, I’d get a ping from his manager asking on why am I blocking the review. If you are in a culture like this, you may as well just ship slop. Management wants to break stuff, that is on them.
I paid my mortgage off by being the insurance policy when that happens.
Re: AI Lazyslop and Personal Responsibility
#8At the end there's a typo "catched" should be caught. Otherwise, agree-ish. There should be business practices in place for responsible AI use to avoid coworkers having to suffer from bad usage.
> Then, I’d get a ping from his manager asking on why am I blocking the review.
The suffering is self inflicted for this particular person. The organization doesn’t value code review.
Re: AI Lazyslop and Personal Responsibility
#9If you get a 1600 line PR you just close it and ask them to break it up into reviewable chunks. If your workplace has an issue with that, quit. This was true before AI and will be true after AI.
I mean, there are some exceptions on when 1600 PRs are acceptable (Refactorings, etc) but otherwise agree.
What really bugs me is that today, it is easier than ever to do this (even the LLM can do this!) and people still don't do it.
Re: AI Lazyslop and Personal Responsibility
#10At the end there's a typo "catched" should be caught. Otherwise, agree-ish. There should be business practices in place for responsible AI use to avoid coworkers having to suffer from bad usage.
He had a typo in the one section where he didn't use AI to copy-edit! But really, copyediting with LLMs is a godsend. I used to struggle with grammar to the point that I had a grammarly subscription. Now, proofreading can even be done locally.