South Africa’s biggest forum. Discuss, discover, and connect with thousands of members.
Good and bad.What is the opinion on Google AI Studio App creation and the code and file structure it generates?
Wow, can you be any less useful? Lol. When did we get this lazy that we respond to a direct question and give a vague meaningless opinion which doesn't help in any way?Good and bad.
Some time today.When did we get this lazy...
Could real programmers please share some good practices and what to check for example the vulnerabilities such as XSS and SQL injection etc.I hope you are adding all your security checks or only using this as an internal project that doesn't touch the internet.
The vibe coded things are coming through in pentests and have huge security flaws.
Even programs that have been pentested aren’t safe. Someone decides to “clean up” the code, dumps it into an AI without any of the context, and the AI strips out chunks that existed for a reason. Suddenly, an application that’s been tested for a decade is vulnerable to XSS, SQL injection, etc.
Could real programmers please share some good practices and what to check for example the vulnerabilities such as XSS and SQL injection etc.
My friend there is no more real developers. We all died out.Could real programmers please share some good practices and what to check for example the vulnerabilities such as XSS and SQL injection etc.
Or basic intuition for this![]()
OWASP Top Ten Web Application Security Risks | OWASP Foundation
The OWASP Top 10 is the reference standard for the most critical web application security risks. Adopting the OWASP Top 10 is perhaps the most effective first step towards changing your software development culture focused on producing secure code.owasp.org
Unfortunately many coders don't have a through security understanding.
Then this is where you step in to save your job and move into a management role. Teach them about peer review and AI governance.This is the world I find myself in.
As a human, having to try and compete with machines and Gen Z that is so "excited about AI" is killing me- that they hand over entire code bases to AI and then the bosses tell the big bosses "Oh quality went down because the staff were slacking sir, we've canceled WFH so it should get better". Quality isn't getting better, AI has removed stuff without context, and now the ship is up the creek, without a paddle. Nobody knows where AI broke the code.. so here we sit, with customers dropping the product one by one, and potential lawsuits, and I sit in the still factory- no production being done because orders dried up.
I am telling you now that my current employer will go tits-up soon.. giving it 10 months tops.. I see the brown stuff heading for the fan.
This has happened because the bosses don't care about anything except the fancy graphs on TFS. Lines of code written in a day and tickets resolved > quality.
And I bet you issues started showing long before AI was introduced. AI is just a tool. Good practice and code review should not disappear.This is the world I find myself in.
As a human, having to try and compete with machines and Gen Z that is so "excited about AI" is killing me- that they hand over entire code bases to AI and then the bosses tell the big bosses "Oh quality went down because the staff were slacking sir, we've canceled WFH so it should get better". Quality isn't getting better, AI has removed stuff without context, and now the ship is up the creek, without a paddle. Nobody knows where AI broke the code.. so here we sit, with customers dropping the product one by one, and potential lawsuits, and I sit in the still factory- no production being done because orders dried up.
I am telling you now that my current employer will go tits-up soon.. giving it 10 months tops.. I see the brown stuff heading for the fan.
This has happened because the bosses don't care about anything except the fancy graphs on TFS. Lines of code written in a day and tickets resolved > quality.
I wasn't at this company at the time but yes. No evidence of any good practices. Code reviews were done but there's no documentation for anything. And on top of that a culture of "need to know" because the former company owner was a paranoid sort.And I bet you issues started showing long before AI was introduced. AI is just a tool. Good practice and code review should not disappear.
I am an uneducated vibe coder. I ask AI to explain everything. Also try to learn and educate myself along the journey. What would never have been possible in my life is now possible.AI is a tool, nothing more.
A recent example is my weekend projects.
I asked AI to write a function for me in C to calculate the CRC-16 of a packet but to use the PROFIBUS variant.
On the backend side, I am writing the code in Golang. It got that right on the first try.
On the front end, a piece of IoT I am making for myself, written in C, it keeps insisting the CRC polynomial is 0x1021.
No big deal, since I understand the code I just modified the offending line of code to make it work.
So yes, AI is a massive time-saver PROVIDED you UNDERSTAND THE CODE AND YOU CAN ARTICULATE WHAT YOU WANT.
If I was an uneducated vibe-coder... the whole thing would not work, and no clue why.
AI does not replace a programmer, it merely provides help with all the KAK jobs, things I can't be arsed to write anymore.
Yes, and that's also a good thing. It will get better as well. The trick is to find the right balance, but also not to think that humans will be replaced outright.I am an uneducated vibe coder. I ask AI to explain everything. Also try to learn and educate myself along the journey. What would never have been possible in my life is now possible.
What would be awesome is if I can follow good enough practice to hand over the fully functional and well implemented project to a senior dev to finalise and push for production, I'm a specially pedantic about security.Yes, and that's also a good thing. It will get better as well. The trick is to find the right balance, but also not to think that humans will be replaced outright.
Before shipping, get yourself a once off sub to a competitor platform, prefreably pay as you go for their most powerful engine, then ask it to critique the code (no changes made), specifically in the security department and according to OWASP top 10... take that output and feed your original LLM, asking it it's 'opinion' on those findings.What would be awesome is if I can follow good enough practice to hand over the fully functional and well implemented project to a senior dev to finalise and push for production, I'm a specially pedantic about security.
In my planning for the prototype, interesting enough Claude has already mentioned implementing OWASP as part of the auditing.Before shipping, get yourself a once off sub to a competitor platform, prefreably pay as you go for their most powerful engine, then ask it to critique the code (no changes made), specifically in the security department and according to OWASP top 10... take that output and feed your original LLM, asking it it's 'opinion' on those findings.
Weigh up for yourself the output from the two based on your own research and see if anything needs to be done. It can be done properly with an LLM but you'll learn alot in the process - that's a big take-away.