Rant about public recruitment category

What’s the point of this rant? I skimmed it but I have a pretty good understanding of what it’s about with just the first little bit as well as the title.

I’d like to remind you that the following thread exists, something which is far too commonly ignored whether that’s deliberate or not.

Don’t complain about other people’s recruitment threads like this, speak for yourself. If you don’t like an offer, move on and don’t take it. If you really feel the need to comment, send them a feedback message privately on how to improve their post to better attract potential developers and team members. If your feedback is unwarranted or declined, brush it off, move on; no point arguing the case further.

You are not either their team leader nor their advisor, so don’t hijack a recruitment thread to talk about how bad their post is or their payment or whatever. Flag it or send them constructive feedback. If you aren’t interested, don’t reply.

Don’t bash other developers for being new and inexperienced to the employer field. Ranting like this isn’t going to change anything and neither is babysitting them through the process, especially since that’s not the function of the forum in any capacity.

When other developers are bashing a newer one for having a lower-quality recruitment post and trying to argue the case extensively, it not only derails the thread (the purpose of all recruitment threads is to hire, not how good you think someone created an offer) and it is counterproductive for them to learn how to better hire.

Developers actually interested in joining are welcome to respond in case they’re looking for slight modifications to the offer before joining or if they wish for clarification on something in the post. This can also be done privately (a la negotiations).

5 Likes

Thank-you, I was feeling the same about this thread. I got offended by some of the remarks because the view he has is very narrowed.

1 Like

Not entirely sure about the ranty aspect, but I think it’s good to have some discussion about the mechanics of development teams.

1 Like

Just want to re-emphasise this post was targeted at inexperienced project leaders and new development teams, I did state several times it excludes formal development teams :slight_smile:

The reason why I brought it up is because almost all of my commissions I get are these requests that have minimal information on what they want. I’m sick and tired of having to log on every day when my commissions are open and see tons of undescriptive, confusing orders that I can’t work on. It’s not just a case of “oh just decline and use common sense.”

1 Like

This is a very normal case for users who are open for commissions and simultaneously a non-problem; again, you’re working with kids and other varying levels of inexperience, immaturity and deliberate or unintentional ignorance. You should be expecting these kinds of messages.

Your case is very much a “just decline it, use a common sense” case. Does it matter if you’re “sick and tired” of seeing these kinds of requests? No. That’s not changing anything. It becomes less of a complaint about the recruitment category and more about users who don’t know how to submit descriptive requests; something that doesn’t belong here.

3 Likes

When creating guidelines you should organize it by most important-least important. Currently your #1 requirement is listed as #8 which can easily be missed if someone is skimming through your document. Clients like easy, uncomplicated systems to abide by. YOUR system is far too complex in comparison to your competition.

The issue is how those that lack experience aren’t aware of the consequences of their actions. A terrible first impression can ruin a business relationship rather quickly. Networking with the right people is one of the key factors of becoming successful as a project leader, having bias built against you will limit your connections severely.

My perspective

The only reason why I was able to familiarize myself with business is because I studied the marketing geniuses for years. I applied their teachings to my failed recruitment attempts in the past whereas most people wouldn’t even fathom self evaluation because it isn’t something that comes to mind. You can’t throw someone into the world than expect the best results, you’ve got to teach them in order to be successful.

Some are self taught and others are taught by the masters. It’s the player’s choice to listen whereas it’s our responsibility to educate them so that the mistakes aren’t repeated. The youth of our generation is going to take over once we move on from this platform whether it be by death or advancing in life. If we don’t prepare them for what they’re getting themselves into than this platforms growth will be halted significantly.

1 Like

It would be nice if you didn’t misquote me as leverage for your own point.

Though the concept of working with young and inexperienced audiences is fair game, my response was directed towards teams/individuals submitting requests to open commissioners, not putting up recruitment posts. The dynamic is different in terms of who’s setting the grounds and who’s negotiating.

It isn’t your responsibility at all to educate people here. The DevForum is a learning platform and what users choose to learn is at their own discretion. Your only expectation is that when you’re replying, you’re being respectful to the community and your posts offer constructive feedback or suggestions for improvement; you don’t force your ideals on others by pushing an issue. If they disagree or don’t want to heed it, move on.

Great speech but it has no ground here.

4 Likes