Earlier quoted context omitted.
> uncovering some frightening immaturity pervasive in Valley companies. This is one of the dark sides to having an entire engineering team in the 25-30 age range. They can sling http just fine, but sometimes don't fully grasp the consequences of their work.
I was 22 when I started and cared very deeply about the consequences of what I was doing. It's more about heavily interviewing for alignment with your mission. If people care deeply about the problem you're solving — not just the technical problem, the people problem — then you're far less likely to have these issues. I interviewed dozens if not hundreds of people at ZP and there were two red flags for engineers: 1)…
So hacking is reserved for research project and the odd on-off script which gets nowhere further than my PC ;)
I've had hackers in my team, they've always been strong technically (they take risks so learn fast) but they have always been a net negative in the long run if left uncontrolled. But put them into the right environment and they can be very effective (as they tend to be very creative).
The question is will an ex-Facebook hacker accept being kept at arms-length production and treated like a junior developer? It works for me because there aren't any AAA employers here in The Netherlands.