@LillyHerself
Early on, I did a bunch of experimentation on how including AI in a project would impact the development process. I did this all on personal time. I concluded that it solves very niche cases that we already solve a different way, and it causes way too many problems.
1/3
AI coding tools Introduce low quality code in large volumes. It spagettifies existing code and makes code reviews so much more painful. It ignores quality gates, demonstrates lack of understanding of how code works, and would probably be the type to ask "what's a design pattern?" because it clearly doesn't know anything about them for practical use. Not to mention that much of the code is simply wrong.
When adding it into a process, you may as well douse us in maple syrup on a hot humid day in a swampy area. Junior devs who still aren't familiar with coding practices and understanding the codebase try to rely on AI slop and it is immediately obvious because it's a lot of fluff that doesn't actually do what you asked them to do. But it looks right if you don't know what's going on.
2/3
Despite this, upper management seems to not care about what the senior engineers have to say because it's contrary to what they (upper management) want to do. The senior devs aren't quiet about it so it's not like it's unclear.
LillyLyle/Count Melancholia
h3mmy 