I like the fact that PMs are showing what they think for a product end-state rather than talking about it. One of our PMs showed a fully functional code for what we need to build.
Problem? it is good on a sandbox, cannot be used for production as complexity comes from actual integration with many other systems which are kinda mocked in sandbox environment with sqlite, some json files etc.
Would I allow them to contribute to my app infrastructure repo?
Honestly, I would not let anyone not fully understanding how it works to do so.
Even newly joined people to the team have developed similar habits of relying on AI to do "simple" things, like change an "exception" to "RuntimeException" that seems like a good thing to do but would actually cause problems as other parts of the code base relied on these "exceptions" for exception handling.
You could argue that if your tests are good enough you may not need to worry but that's BS, and this is my personal take.
I like the fact that PMs are showing what they think for a product end-state rather than talking about it. One of our PMs showed a fully functional code for what we need to build. Problem? it is good on a sandbox, cannot be used for production as complexity comes from actual integration with many other systems which are kinda mocked in sandbox environment with sqlite, some json files etc.
Would I allow them to contribute to my app infrastructure repo? Honestly, I would not let anyone not fully understanding how it works to do so.
Even newly joined people to the team have developed similar habits of relying on AI to do "simple" things, like change an "exception" to "RuntimeException" that seems like a good thing to do but would actually cause problems as other parts of the code base relied on these "exceptions" for exception handling.
You could argue that if your tests are good enough you may not need to worry but that's BS, and this is my personal take.