mattkenefick

Read more into things than you need to given the opportunity.

Let's say you need an icon for something, but don't know much about design. Once in a while, try making it on your own. Learn about the pen tool, image formats, etc.

Let's say you need a simple SELECT from MySQL. Read more into how they actually work under the covers, in large-scale environments, or how they change for MSSQL / Postgres.

Let's say you need a particular jQuery function.. take a few minutes to read the source and see what it's actually doing.

If you take a few minutes each time you do something unfamiliar, you'll gradually build up a better understanding and larger skillset without having to put in too much effort.

"but I'll still keep coding based on that assumption."

That's terrible advice. If you're unsure of what you're supposed to be doing, you should close the computer and start exploring your options with pen and paper before doing more damage.

If you keep going based on assumption, you drive halfway across the country in the wrong direction like in Dumb and Dumber.

Sometimes it's better to do nothing at all than to inflict damage because you didn't know what you were supposed to be doing.

Lately, instead of greeting people with "Hello" or "Hey man," I usually start off all my conversations with this speech.

I agree so much so I had to double check that I didn't actually write it.

Sounds like you were one of the interviewees.

I don't see the "geeky" aspect of it. It reminds me of golf + pool.. neither of which are geeky.

Looks good.

I came to the comments for this. I immediately liked the left way better, and then saw "If you said right one, then I did my job." I stopped reading after that because he obviously didn't do his job.

"In contrast with a photomosaic," ehhh.. it's just a photomosaic.