/explore
|
You are here 
|
dylanbeattie.net | ||
| | | | |
blog.valentin.sh
|
|
| | | | | [AI summary] An article arguing that 'vibe coding' is a poor developer experience because relying on AI agents to generate code without writing it manually is analogous to maintaining generated metaprogramming output, which is inferior to using proper software abstractions. | |
| | | | |
nonint.com
|
|
| | | | | [AI summary] The author describes spending two hours 'vibe coding' to generate an advanced ML algorithm that would take them much longer to verify fully, highlighting the challenges of trusting AI code. | |
| | | | |
simonwillison.net
|
|
| | | | | Vibe coding is having a moment. The term was coined by Andrej Karpathy just a few weeks ago (on February 6th) and has since been featured in the New York ... | |
| | | | |
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. | ||
