Programming fun ranks don't mean anything and some of them are out of date. I've got "VB Programmer" rank for example, but VB hasn't been relevant in over a decade. There's a SCAR Programmer one floating around too, and SCAR hasn't been relevant for even longer than that. Most of the programming fun ranks are held by old, inactive users.
I think the site should either commit to having some sort of official framework/guidelines on obtaining or changing a programming fun rank, or to remove them altogether. Whenever I've brought something up like this in the past it's always been delegated, nebulously, to Matthew or Sythe, without anything happening.
What committing would look like:
- Set requirements for obtaining the rank. X years since registration, and commitment to the community through code in some capacity (e.g. writing free bots/scripts for the community, posting tutorials, etc)
- Someone, other than Sythe or Matthew, who manages these ranks
- Someone who keeps the ranks up to date. The VB rank shouldn't exist anymore, but there is a .NET rank, so anyone holding the VB rank should just get that (or re-apply or whatever).
The easy route would be to just remove them but I think that'd be lazy and short-sighted.
I think the site should either commit to having some sort of official framework/guidelines on obtaining or changing a programming fun rank, or to remove them altogether. Whenever I've brought something up like this in the past it's always been delegated, nebulously, to Matthew or Sythe, without anything happening.
What committing would look like:
- Set requirements for obtaining the rank. X years since registration, and commitment to the community through code in some capacity (e.g. writing free bots/scripts for the community, posting tutorials, etc)
- Someone, other than Sythe or Matthew, who manages these ranks
- Someone who keeps the ranks up to date. The VB rank shouldn't exist anymore, but there is a .NET rank, so anyone holding the VB rank should just get that (or re-apply or whatever).
The easy route would be to just remove them but I think that'd be lazy and short-sighted.
























































































































