Explore >> Select a destination
|
You are here 
|
www.securityjourney.com | ||
| | | | |
simonroses.com
|
|
| | | | | [AI summary] A retrospective on the evolution of software development from manual coding to AI-generated code and the associated changes in security vulnerabilities and management. | |
| | | | |
compositecode.blog
|
|
| | | | | Explore the future of software development as AI transforms coding, and learn how to adapt with effective management practices. | |
| | | | |
www.blackduck.com
|
|
| | | | | Explore the concept of vibe coding, its benefits, risks, and best practices. Learn how to harness AI-assisted development while maintaining software security and integrity. | |
| | | | |
nmn.gl
|
|
| | | Last Tuesday at 1 AM, I was debugging a critical production issue in my AI dev tool. As I dug through layers of functions, I suddenly realized - unlike the new generation of developers, I was grateful that I could actually understand my codebase. That's when I started thinking more about Karpathy's recent statements on vibe coding. For those who missed it, Andrej Karpathy recently shared his thoughts on what he calls "vibe coding" - essentially surrendering code comprehension to AI tools and hoping for the best. His exact words? "I 'Accept All' always, I don't read the diffs anymore." I have learnt a lot from Karpathy and use AI tools daily, but there's a world of difference between augmenting your capabilities and completely surrendering your understanding. | ||
