Explore >> Select a destination
|
You are here 
|
github.blog | ||
| | | | |
cline.bot
|
|
| | | | | The model-agnostic, IDE-agnostic, inference-agnostic, open-source coding agent that 3 million developers trust-now with enterprise security, governance, and observability at scale. | |
| | | | |
brianchristner.io
|
|
| | | | | Discover how GitHub Copilot and ChatGPT have revolutionized the way developers work. Uncover the potential pitfalls and triumphs that arise when AI takes the reins of coding. Get ready to embrace the future of programming, where human and machine collaborate seamlessly. | |
| | | | |
github.com
|
|
| | | | | A curated list of vibe coding references, collaborating with AI to write code. - filipecalegario/awesome-vibe-coding | |
| | | | |
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. | ||
