,
3 tweets,
1 min read
Read on Twitter
It's important to be able to do both. You have to understand why something works to be able to code properly. But once you DO, and as long as you always go to that effort when trying new things, Googling for syntax etc is fine. No one can remember everything.
Just never 'black box' code. One of the few things one of my developers can ever say to me which I'll shut them down hard on is:
"I copied this and it works, but I'm not 100% sure why"
If you don't know why, deconstruct it until you do. Otherwise how can you ever debug it?
"I copied this and it works, but I'm not 100% sure why"
If you don't know why, deconstruct it until you do. Otherwise how can you ever debug it?
If you need help to do that - guides, pair coding, more Google, whatever then that's fine.
But you MUST understand the principles on which it works. Otherwise you're just creating delayed pain for yourself and others down the line.
But you MUST understand the principles on which it works. Otherwise you're just creating delayed pain for yourself and others down the line.
