I didn't say it should be the main focus. Also, your comment demonstrates my point (thanks for that). It's arrogant, and demonstrates a lack of insight. If they don't, Yo should care. As I mention in another comment below, this impacts their reputation. Imagine if the developers of Yo build something that really should be secure one day. First thing I'd think is they don't bother with security, so I won't use that app. Or the developer interviews somewhere else one day -
Interviewer: "So dude, what have you done in your career?"
And as selfishly awesome as it would be for my career if security holes became career-ending mistakes (hire me so you don't lose your job!), the only people who haven't written software with security holes are those who haven't written software.
Comments
I didn't say it should be the main focus. Also, your comment demonstrates my point (thanks for that). It's arrogant, and demonstrates a lack of insight. If they don't, Yo should care. As I mention in another comment below, this impacts their reputation. Imagine if the developers of Yo build something that really should be secure one day. First thing I'd think is they don't bother with security, so I won't use that app. Or the developer interviews somewhere else one day -
Interviewer: "So dude, what have you done in your career?"
Yo dev: "I built Yo."
Interviewer: "Yo got hacked. Goodbye."
. . . said no interviewer ever.
And as selfishly awesome as it would be for my career if security holes became career-ending mistakes (hire me so you don't lose your job!), the only people who haven't written software with security holes are those who haven't written software.
I get it. Because absolute security is an impossibility, we just shouldn't bother at all.
See what you and I did there? Extremes, both sides of the argument. I know that no interviewer says that - it was done to illustrate my point.