827 karma · joined April 18, 2012
The privacy of "?". Was waiting for this part since it was included in the title.
Ping me with original open source work and contributions. https://cloudup.com/cXTFuFL2SSU
I look for good naming, organization, and how easy a new developer will be able to ramp up given the environment he or she has established.
Here's a link to the job description. https://jobs3.netmedia1.com/cp/faces/job_summary?job_id=WAT-...
Recruiter: "What were you looking for in terms of salary?" Me: "[figure]" R: "Is that in line with what you're currently making?" EVERYONE EVER: "YES".
What a complete and utter waste of time. Who is going to say no?! They have no way of (legally) verifying any of your private salary data.
I once had a recruiter try to scare a friend saying he would access his public tax info. That recruiter should have been arrested.
https://www.google.com/about/careers/search#!t=jo&jid=45100&
http://kevinsuttle.com/posts/the-right-questions-to-ask-mobi...
http://kevinsuttle.com/posts/the-right-questions-to-ask-mobi...
URL Design is key. I often refer to the naming chapter of Uncle Bob's Clean Code book for this. This also helps with consistency and predictability, which in turn, makes writing docs easier.
I've got an API Design Readlist, which I've added this thread to. http://readlists.com/6c5c6009/
https://twitter.com/kevinSuttle/status/513446291968651264 https://twitter.com/kevinSuttle/status/513447060499341313