Security Shifting Left in Lovable

I've been at LedBy Community Hackathon this afternoon. We got a few free tokens to get a chance to play with creating something with Lovable. (Did I create a new community? Yes I did!)

I'm not sure I'll do anything with it. I've played with Lovabable in the past, it's great and empowering. And even using it only two months after I last did, I can see how much it has improved.

What pleasantly surprised me today, was that upon trying to publish my project it highlighted some security problems that needed fixing before going live. This makes me happy. Thinking about quality early, shifting left, so to speak. I think we'll be seeing more of this as AI things continue to improve.

I still find myself spending alot of my time in Lovable testing and thinking things through. It's not all about the building. Everything we create needs testing, verifying, checking and whatever you may want to call it. I still worry about the problems I can't see, but at the same time many parts have good practices built in, or so it seems. Don't quote me on that!

Of course, we can apply more critical thinking. Rather than just accept the issues raised and get the AI to fix it. If I were doing this more professionally, and wanted to create this into a project, I would be paying more attention to what the security issues were, explore them and consider what the quality and security mean.