Slide 1

Slide 1 text

How to become a Better Developer

Slide 2

Slide 2 text

No content

Slide 3

Slide 3 text

This code could be better

Slide 4

Slide 4 text

I could be better

Slide 5

Slide 5 text

Skill Plateaus

Slide 6

Slide 6 text

Challenge Yourself

Slide 7

Slide 7 text

Expose yourself to new experiences

Slide 8

Slide 8 text

“Here’s the thing: After that initial explosion of cognitive growth, they noticed a decline in both cortical thickness, as well as the amount of glucose used during that task. However, they remained just as good at Tetris; their skill did not decrease. The brain scans showed less brain activity during the game-playing, instead of more, as in the previous days. Why the drop?

Slide 9

Slide 9 text

~ Andrea Kuszewski, “You can increase your intelligence” Their brains got more efficient. Once their brain figured out how to play Tetris, and got really good at it, it got lazy. It didn’t need to work as hard in order to play the game well, so the cognitive energy and the glucose went somewhere else instead.”

Slide 10

Slide 10 text

Do It

Slide 11

Slide 11 text

You are functionally blind when you only have book knowledge. Chong Kim

Slide 12

Slide 12 text

Study the masters

Slide 13

Slide 13 text

Learn the classics http://www.flickr.com/photos/zitona/3616391791/

Slide 14

Slide 14 text

You might call some of these things “computer science”, but many of the best programmers I know have no formal training in such. These things can be learned by anybody, many of them are learned best in a hands-on environment. Jesse Storimer

Slide 15

Slide 15 text

Investing your time learning things like networking, concurrency, regexes, or system programming will not go out of style in your lifetime. Jesse Storimer

Slide 16

Slide 16 text

Practice mindfully http://www.flickr.com/photos/sigurdr/5335958665/

Slide 17

Slide 17 text

No content

Slide 18

Slide 18 text

No content

Slide 19

Slide 19 text

Mind your body http://www.flickr.com/photos/imagesbywestfall/3896838102/

Slide 20

Slide 20 text

Grit

Slide 21

Slide 21 text

One day a monk visited Master Wq, and inquired, “Master, how will my code be different when I have mastered Vim?” Master Wq answered, “Before Vim: declare, define, process, print. After Vim: declare, define, process, print.” ~ Vim Koans

Slide 22

Slide 22 text

I’m not hiring

Slide 23

Slide 23 text

(Sorry)

Slide 24

Slide 24 text

http://nuclearsquid.com Questions?