Pending “Withdrew” staff app prefix

There's value to that idea and as far as I'm aware would be a 5 minute job in the forum backend.
That being said, I think the value is less than 5 minutes worth of effort.

For the staff side of things; If someone reapplies, their previous apps are normally reviewed as well. Whether they withdrew or were denied, whatever feedback was left on the app can be pertinent and needs to be read anyway. In the course of doing so, they would also see the closing statement, highlighting that it was withdrawn.
It's generally speaking such a rare occurrence that I don't think the change is needed for the few outliers. But if a dev or lead wants to, there's really no harm in it. +0
 
+1, in the sense that I believe the distinction between the two terms is very important. Although I agree with Siddo that the feedback/reason for closure will typically just be read anyways
 
-1; and it's actually for the same reason @Random Props threw a +1 out there.

I do think that there is a distinction between a withdrawn app and a denied app. However, because there is that distinction, I think by having that tag and recognizing the difference that people will ultimately withdraw their application before a foreseeable denial which will ultimately make the tag worthless. It's kind of like having an employee resign rather than being fired because of the negative connotation behind it. I also am concerned that an applicant will withdraw their application early if they perceive their application not going well for the sake of having a withdrawal rather than a denial.

I just think it's better to call it a denial and to look in to the context of why it was a denial. That should happen anyways, and I think having a "Withdrawn" tag just adds to some unnecessary mental games during an application period.
 
-1; and it's actually for the same reason @Random Props threw a +1 out there.

I do think that there is a distinction between a withdrawn app and a denied app. However, because there is that distinction, I think by having that tag and recognizing the difference that people will ultimately withdraw their application before a foreseeable denial which will ultimately make the tag worthless. It's kind of like having an employee resign rather than being fired because of the negative connotation behind it. I also am concerned that an applicant will withdraw their application early if they perceive their application not going well for the sake of having a withdrawal rather than a denial.

I just think it's better to call it a denial and to look in to the context of why it was a denial. That should happen anyways, and I think having a "Withdrawn" tag just adds to some unnecessary mental games during an application period.
Honestly didn't even think about that scenario; very valid point
 
-1; and it's actually for the same reason @Random Props threw a +1 out there.

I do think that there is a distinction between a withdrawn app and a denied app. However, because there is that distinction, I think by having that tag and recognizing the difference that people will ultimately withdraw their application before a foreseeable denial which will ultimately make the tag worthless. It's kind of like having an employee resign rather than being fired because of the negative connotation behind it. I also am concerned that an applicant will withdraw their application early if they perceive their application not going well for the sake of having a withdrawal rather than a denial.

I just think it's better to call it a denial and to look in to the context of why it was a denial. That should happen anyways, and I think having a "Withdrawn" tag just adds to some unnecessary mental games during an application period.
Amazing point and I gotta agree, but I think there is a way to get around this. If a person applying for staff is very obviously not gonna get it, they should not be able to withdraw, or if they do, just use denied instead of withdrew.
There’s almost definitely a better way to handle this than what I just said so if you have any ideas tell me
 
If a person applying for staff is very obviously not gonna get it, they should not be able to withdraw, or if they do, just use denied instead of withdrew.
This would be more of the same silly politics that helix highlighted.
When is it "very obviously"?
Are staff just punishing me for applying now, 'cause they denied it even though I withdrew it and I see other withdrawn apps on the list?
I remain neutral on the suggestion all in all, but helix has raised some valid points about the downsides to implementing this.

Another point to consider;
Fundamentally, a denied app is not necessarily a bad thing.
Sometimes an app is denied because it's too early to be applying. Sometimes because the homie needs to execute on feedback. Sometimes because there's no sense in stringing someone along when their app wouldn't be accepted for a month+ anyway.
In a sense, a denied app is partially wiping the slate clean; people will still go back and read the first one. But then people start comparing that app against the way you've been recently - and if you have made any improvements others wanted to see, that typically convinces people that you're worth a shot.

TL;DR: Denying an app and letting the homie reapply after a month's time lets them come back stronger. People have in the past had a massive -1 app be followed up by a massive +1 reapp.
 
Back
Top