Do you mean like company policies?
These are a good place to start, when considering making company policies:
workable
template
Well I'm probably wrong, but to me its synonymous with application security.
Application security actually seems a bit hard to define. Code may be secure and still be used to harm others. It may be secure but and still used in ways it wasn't assigned to allow.
I guess you need a set of constraints about what the code should and should not do in order to define what secure means for it?
(Code safety sounds a bit different to me, don't know if that's based on anything. I'd interpret it as not containing bugs, and perhaps even it not being to easy to introduce bugs. Largely synonymous with code quality I guess. And mostly a superset of security, as most safety concerns are bugs but not all bugs are safety concerns. Perhaps I'm inventing my own meaning for words though...).
it depends, to some degree I go with Jason Knight because it really depends on your perspective. As a javascript developer I probably don't have to build in canaries in my memory control to avoid highjacking those address registers like in C.
It is really layered, isn't it?
I have to say, I don't know .... it's so much .... it's actually so generic to me it's useless without context.
Jason Knight
The less code you use, the less there is to break
You ask ten different people, you'll probably get ten different answers. The term itself is too vague, has different meanings based on which language you are using ALONE, and on the whole seems more often used as a sick buzzword than having any actual meaning.
But then I've got a background in ADA. The compiler won't let you write insecure code.