Loading video...

Video Failed to Load

Go Home

AI coding or Vibe coding as they call it these days helps to write code faster has been helping to produce applications really fast. It is great for prototyping but without careful consideration, you might be in for a disaster. There are extra measures to take into consideration to...

14,641 views • 4 months ago •via X (Twitter)

0 Comments

No comments available

Comments from the original post will appear here

Related Videos

I'm teaching a new course! AI Python for Beginners is a series of four short courses that teach anyone to code, regardless of current technical skill. We are offering these courses free for a limited time. Generative AI is transforming coding. This course teaches coding in a way that’s aligned with where the field is going, rather than where it has been: (1) AI as a Coding Companion. Experienced coders are using AI to help write snippets of code, debug code, and the like. We embrace this approach and describe best-practices for coding with a chatbot. Throughout the course, you'll have access to an AI chatbot that will be your own coding companion that can assist you every step of the way as you code. (2) Learning by Building AI Applications. You'll write code that interacts with large language models to quickly create fun applications to customize poems, write recipes, and manage a to-do list. This hands-on approach helps you see how writing code that calls on powerful AI models will make you more effective in your work and personal projects. With this approach, beginning programmers can learn to do useful things with code far faster than they could have even a year ago. Knowing a little bit of coding is increasingly helping people in job roles other than software engineers. For example, I've seen a marketing professional write code to download web pages and use generative AI to derive insights; a reporter write code to flag important stories; and an investor automate the initial drafts of contracts. With this course you’ll be equipped to automate repetitive tasks, analyze data more efficiently, and leverage AI to enhance your productivity. If you are already an experienced developer, please help me spread the word and encourage your non-developer friends to learn a little bit of coding. I hope you'll check out the first two short courses here!

Andrew Ng

1,223,694 views • 1 year ago

Vibe-coding a product will 100% get you hacked unless you are careful. Here are 10 suggestions to avoid a disaster. Remember, vibe-coding is meant to be fun, but you should never be trusting or careless. Modern AI can help you fix security vulnerabilities, but you must know what questions to ask. This advice is for both experienced developers and newcomers. We are all noobs at least 3 times a week and twice during weekends. Personally, I'm the most careful when working with AWS. It's a large platform with many traps. I've used AWS for 15 years, and while I might not make rookie security mistakes, I wouldn't trust myself with anything that's high-stakes. But things have changed! Before, I had to pay security experts to assess my code. Today, I use Amazon Q Developer (a Visual Studio Code extension—or you can also use the Q CLI) to find and fix issues. By the way, AWS is sponsoring this post, and I hope you find the security recommendations below as helpful as they did when they agreed to work with me. Before deploying anything to my AWS account, I go through the following security checklist with Q's "/review" agent: 1. I start with any infrastructure config files (Terraform, Cloud Formation, etc.) and ask Q to find security vulnerabilities. 2. I then ask it to scan the code for hardcoded credentials, API keys, database passwords, or any other secrets in the codebase. 3. I ask the assistant to look for open ports, unrestricted inbound traffic to your servers, and unsecured endpoints. 4. I ask for suggestions for least-privilege policies. 5. I ask it to verify that no data is publicly accessible and ensure that all data is encrypted at rest and during transit. 6. Identify any lack of rate limiting to avoid DDoS attacks. Ask for suggestions on how to prevent Cross-Site Scripting and Cross-Site Request Forgery attacks. 7. Ask it to scan the project for vulnerable dependencies with pip, npm, go modules, or docker images. 8. Scan the code to find temporal resources, unused user accounts, and orphaned cloud assets. 9. I ask it to identify any forms with insufficient input validation. 10. Finally, I ask for suggestions on how to improve logging throughout the code. This might not be an exhaustive list, but it helps me cover glaring holes.

Santiago

47,933 views • 1 year ago