Hi everyone, I need some perspective from the community. I work as a NetSuite Developer, and my background is mostly backend and business logic. I have zero professional experience working on dedicated frontend projects, just some basic fundamental knowledge. Lately, I've been creating a lot of custom UIs and client-side apps using Suitelets in NetSuite. Because I lack proper FE architecture knowledge, my approach is pretty random—just building whatever comes to mind as long as it gets the job done (usually a mix of vanilla JS, basic jQuery, and pure HTML). The end results are fully functional and the business logic works perfectly. However, the UI/UX, interactivity, and code structure on the client side are definitely lacking. I've recently started using AI to handle the FE side (like generating Vue components, Bootstrap styling, and managing DOM interactions), and it's been a game-changer. My question is: Is it safe/acceptable to rely entirely on AI assistants to manage the frontend architecture and UI coding in this context? How do you guys (especially backend/ERP devs) handle frontend requirements when it's not your strong suit? Any insights or advice would be greatly appreciated!

That sounds like the story of my NetSuite career too. My opinion currently is: I would not trust the AI completely even for the front end (though I would more than for the backend), because the UI is how inputs are made to the system, and in NetSuite, a frontend can be given power to do things that only the backend should be allowed to do. This is usually controlled though, through Role permissions. But again, a Suitelet can bypass those since the backend can run as Admin even if the front end doesn't. All that to say, you really need to look over the code yourself and put in safeguards and validation and sanitation. Especially when Suitelets tend to function for both the front and back end from the same .js code file with the same deployment and script parameters. That's from the security perspective. Also consider that you'll want to ensure that it behaves correctly in each use case. Exercise a ton of caution with Suitelets that are available without login (I don't create these unless there's no other way).