|
You are here |
mikeindustries.com | ||
| | | | |
jaysignorello.com
|
|
| | | | | These are the lessons I've learned from the experiences of over a decade of managing remote teams, compiled into a list of core principles. | |
| | | | |
www.range.co
|
|
| | | | | Leading a remote or distributed team? These 5 lessons will help you navigate and overcome the most common challenges facing your team. | |
| | | | |
resources.owllabs.com
|
|
| | | | | Hybrid work is growing in popularity. Learn how managers can lead effective hybrid teams with clear expectations, great tech, and consistent support. | |
| | | | |
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. | ||