1,828 karma · joined March 6, 2008
Developers are people. To hire them you have to establish a relationship with them. If you try to shortcut that, you're gonna have a bad time. It's a long-term game. Yes, you can get some attention with parties and other stunts. That is no guarantee of quality or retention and it isn't sustainable. pastProlog nails it elsewhere on this page.
It might not be the best route because while it will provide individual immunity, HIV transmission can and likely will still happen. The worst case seems to be everyone gets HIV but everyone is a controller.
(Btw, the FAQ seems to have changed since that quote: http://www.immunityproject.org/faq)
The theme in the post that resonated with me is that we're subject to waves in the day, the year, etc.. This jibes with my experience. We're only so effective at any given time, and certain times we're far more effective than others.
Rather than trying to create more of those times, I've come to the conclusion that I already get plenty of those times. I just don't always see it. Realizing this, life becomes more like surfing: sharpen awareness of opportunity, be ready when the opportunity comes, and then ride it to see where it takes you.
One (of many) good things about collective code ownership is that this sort of blame game can't last very long.
- Technical leadership reaching out. Not a recruiter. HUGE. Do this.
- Personal! Actual knowledge of who you are as a developer. Not just a quick scan of github and then a project name drop. (Literally had this happen to me yesterday. Ick. And soooo obvious.)
- Early appeal to "what's in it for me?" and "who will I work with?" BEFORE the "who are we?" bit.
- Dogfooding in the email. Nice touch.
Downers:
- The popped-collar, Natty Ice tone. Kind of a filters out the non-bros. But I guess it tells you about the company culture...?
- I don't know if this job is remote or local, but if it's local, show me pictures of where I'll work.
I understand why Kyle wasn't receptive (and love the creative response), but this is probably enough to move a lot of people on to that next step of the face to face meeting. Personally, I'd probably do the Hangout just to see. Now if it was Worldstar, that would be a whole other matter.
Brick walls have a very high level of observability. A non-bricklayer can look at a wall and tell if it fills the space it is supposed to fill, if the wall is obviously crooked or warped, if bricks are missing, and if mortar is missing between bricks. They can do all of this with very little expertise because they can physically inspect the wall and they have also seen many walls before and have internalized some norms for walls.
Compare this with a non-programmer's experience with software. All they see is the user interface, which is usually a very small part of the whole. Software has a very low level of observability.
Brick walls - typically - are also very simple systems when compared to software such as what is described in the original article. Lower complexity combined with a high level of visibility and broadly shared expectations means that lay people can make many more accurate judgements about a wall, the progress of a wall, the quality of work being done on a wall, etc. without being experts on wall building or brick laying.
This is not to take away from expert tradespeople or diminish their value. It's just a completely different situation which I believe was the intent of the original analogy.
My point was that IQ and/or technical competence are no assurance that you won't make really, really bad choices in life.
This is the best part of their story. Just because a person does technical work doesn't exclude them from being a moron.
*edit: I a word
What is important to understand here is that these processes are highly variable and there is an element of luck involved. It's just the nature of a human-driven process and a complicated organization.
>Reality can be annoying sometimes.
Don't understand this part.
This is a tad disingenuous.
Fingerprint 101:
Fingerprint databases don't search images of your fingerprints. They search mathematical representations of your fingerprints.
To uniquely identify your fingerprint an image is scanned for unique features called "minutia points"[1]. The spacing and orientation of those points is what is stored and later searched for.
Fingerprint matching isn't boolean. When you do a database search you get a list of high probability matches. There are no perfect matches, even between two different images of the exact same finger. Everything is based on probability. For law enforcement purposes, strong matches result in a technician reviewing actual images and making comparisons. For biometric security like this (which is not my area) I expect that there is a threshold percentage match that must be met.
The reason this quote concerns me is that while the actual image can't be reproduced, the image isn't the part that matters! The "mathematical representation" is what counts.
Whether or not that information is actually secure onboard the phone, I don't know.
[0] I have worked with fingerprint processing systems.
[1] http://en.wikipedia.org/wiki/Fingerprint_recognition#Minutia...