[ SECRET POST #6052 ]

[case]

⌈ Secret Post #6052 ⌋

Warning: Some secrets are NOT worksafe and may contain SPOILERS.


01.



__________________________________________________



02.



__________________________________________________



03.
[Etrian Odyssey III]



__________________________________________________



04.



__________________________________________________



05.



__________________________________________________



06.
[Apostle]

























Notes:

Secrets Left to Post: 01 pages, 18 secrets from Secret Submission Post #865.
Secrets Not Posted: [ 0 - broken links ], [ 0 - not!secrets ], [ 0 - not!fandom ], [ 0 - too big ], [ 0 - repeat ].
Current Secret Submissions Post: here.
Suggestions, comments, and concerns should go here.

Comments

[(Anonymous)]

I think this stretches the term to an illogical conclusion.

When figuring out who to hire, for most jobs that involve working with people as well as doing some task, the point is partly qualifications and partly trying to pick someone who will get along with the existing workforce. The company is at a disadvantage when it has to pick between unknown candidates, but if one or more of the people already doing the job are willing to put their reputation on the line and vouch for a potential employee, that's often job-relevant information. It can backfire, but there are a lot of situations where new people feel more of a responsibility to learn quickly and do a good job when they're working with their friends.

Whereas, with family nepotism or other kinds of in-group-ism, there's an implicit assumption that, one, someone else might have been more suited to the work and wasn't hired, and two, the person who was hired might slack off because they think the chances of their ever losing the job are much lower.