SRL Archive - Devs' Corner

This poll is to vote Traveler into a position of reflection developer.
Votes are anonymous thus far.

Examples of his work:
http://villavu.com/forum/showthread.php?t=60389
http://villavu.com/forum/showthread.php?t=60259
http://villavu.com/forum/showthread.php?t=60243

PROS:
- Uses IRC A LOT, exactly what we need from an active developer
- Shows solid knowledge of the core
- Has created great scripts with reflection that people are recieving and commenting on how well it works
- Has been helping out before I even made the app thread which shows this isn't because I posted the thread
- Standards seem good
- Has worked with me on several projects, has good ideas
- Even submits his own color stuff to the reflection SVN, broad knowledge base
- Very friendly, great attitude

CONS:
None that I can think of at the moment


I personally recommend him. All my time working with him, thus far, has been very enjoyable. He solves problems when given to him, knows our staff well and frequents our Reflection chat channels. He even commits stuff during finals time, very impressive.
His knowledge base takes him through the client, he may be learning how to make his own hooks and stuff like that soon. Potentially quite useful person.


What do you think?
I will not vote until discussion happens…etc as I said before in Bad Boy JH's thread.

My feelings about traveler are about the same as those about Bad Boy. I've never talked to him, so I don't know him very well.

He has expressed interest in reflection for a while, active on IRC, and created some neat scripts. So of the current standards for reflection dev:

    * Understand SRL
    * Can code Reflection comfortably
    * Able to make new useful include functions, and will do so once promoted
    * Have posted your examples in this sub-forum (doesn't have to be committed/accepted, as long as it shows you know the reflection core)
    * Know the standards and apply with codes near or at perfect standards (See Nava2's post on standards, which I will provide by edit at the end of this file)
    * Active SRL forum-comer (you don't need to have a stupid-high activity rating like 90%+ though)

He understands SRL (shown by SRL Member), can code reflection (shown by reflection scripts), made procedures/functions/methods (see OP), and pretty active on SRL. I personally don't know the standards like the back of my hand because my only standards are about readability. So its not my place to judge that.
Based on the above and since I'm in support of more people on the reflection SVN to help handle suggestions and build more functions, I'd vote yes (he fulfills both goals). But, I'd also like to see some discussion before voting.

One thing that impressed me about Traveler is how he will tackle any task. When he went to tackle the login task, he learned all the stuff and created a functional thing that the SRL devs didnt do for a while (thought it should be updated by now :) ), this will fare well for him if he becomes a developer since no task will be too far outside his reach.

Excluding client/hook stuff, that is

he might come to learn client/hook stuff if you give him a challenge in that direction ;)

If you guys publish your findings as you go, other people can learn from the steps you took ;)

That's why few people at SRL know how to deal with the clients / hooks. People learnt it elsewhere and those who know, know, those who don't, don't.

~RM

From: Sir R. Magician
he might come to learn client/hook stuff if you give him a challenge in that direction ;)

If you guys publish your findings as you go, other people can learn from the steps you took ;)

That's why few people at SRL know how to deal with the clients / hooks. People learnt it elsewhere and those who know, know, those who don't, don't.

~RM

There are numerous resources out there for people to use, in the form of downloads, threads, and people. If someone isn't able to use those to their advantage, I'm not going to spoon feed them the answers they are looking for. I welcome people to ask me questions about the client if they're truly interested in learning, but most people are looking for a quick fix without putting in the time to really learn how things work.

From: Method
There are numerous resources out there for people to use, in the form of downloads, threads, and people. If someone isn't able to use those to their advantage, I'm not going to spoon feed them the answers they are looking for. I welcome people to ask me questions about the client if they're truly interested in learning, but most people are looking for a quick fix without putting in the time to really learn how things work.

I don't want one nor the other…

I want to understand the concept. The idea behind it..

I don't want to be learning something for which I have no use (no ideas)

~RM

I think this is kinda ridiculous.

Why are there so many applications flying up.. Applications should be done by the applicant, and should be treated as a resume/cover letter.

This informal crap is annoying.

From: Nava2
I think this is kinda ridiculous.

Why are there so many applications flying up.. Applications should be done by the applicant, and should be treated as a resume/cover letter.

This informal crap is annoying.

We could make it so they have to apply formally if you want.

Ideally the goal is to open up applications so that reflection can develop more. The ref. team thus far will be more than capable of preventing the crap scripters from getting in, therefore leaving us with more people to develop. There's just so much to be done and so many ideas that I have to put forth that I can't do it all, even if I was given a ton of time. Many people AFAIK were desiring to be a reflection developer, so I told them to show their work and see how it went.
Does formal or informal matter? IMO as long as we recruit solid people who keep the reflection core perfect/up-to-date/reliable, it's all good. That's just me though.


Plus, it might get more people in from the java/hook based stuff. We need more people like that. We're blessed to have pyroryan, but if he dies, we're pretty much back to ground zero and stuck in a pond of going no-where almost, or even scavenging like vultures for hooks from other updaters.


Train moving forward is better than no train moving at all.



Also for clarification, they did all send us a PM (or maybe just me), so I relayed it here :p

Traveler seems like a solid person. Not judging his skills.

~RM

Too soon.

I don't see why he would need to be developer at this time, he haven't expressed himself in that way, nor developed something out of the ordinary.

From: Naike
Too soon.

I don't see why he would need to be developer at this time, he haven't expressed himself in that way, nor developed something out of the ordinary.

Take into consideration that cstrike is trying to get more active people developing.

Don't raise your standards too high - that's why colour Developers get a new dev once or twice a year - impossibly high standards, while there's a lot of active and skilled enough people out there, ready to maintain the include.

~RM

From: Sir R. Magician
Take into consideration that cstrike is trying to get more active people developing.

Don't raise your standards too high - that's why colour Developers get a new dev once or twice a year - impossibly high standards, while there's a lot of active and skilled enough people out there, ready to maintain the include.

~RM

I'm not raising the standards.
But you need to show me that you can, and will develop for the include to get commit access.
Not just by some simple function(s).

He's on the right path, he's just not there yet.