Explore >> Select a destination
|
You are here 
|
blog.fastforwardlabs.com | ||
| | | | |
www.intuit.com
|
|
| | | | | Learn more about the different types of AI, machine learning, and data science jobs. | |
| | | | |
engineering.zalando.com
|
|
| | | | | Architecture and tooling behind machine learning at Zalando | |
| | | | |
vickiboykis.com
|
|
| | | | | What's different about LLMs versus traditional ML | |
| | | | |
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. | ||
