IMO you gotta be careful with LLMs when you're programming. The temptation to be productive instead of understanding is big. 

Some practices I try to keep in place (I'm not perfect)
- Treat AI like a senior dev: only ask them when you have exhausted all other methods like Googling or docs
- When you get an answer, take the time to stop and really learn why it gave you that code. Maybe think through if it will actually work before running it. 
- Turn off copilot for reason 1; you don't want AI injected code if you didn't ask for it

A dev's greatest assets are their problem solving skill, existing knowledge, and knowing where to go next. Don't let AI make you dull. 

https://x.com/benjamincrozat/status/1805139653533528411

Production without understanding, creation without taste, knowledge without wisdom, facts without context or insight. A world built on skipping steps. Tread lightly!

icebreaker.xyz/0xen |
https://gallery.so/Oxen/galleries | https://opensea.io/collection/farcats

Interesting perspective! How do you think we can strike a balance between efficient production and ensuring understanding and wisdom are not overlooked? What steps can individuals and organizations take to prioritize depth and insight in a world often focused on rapid output?