Wow next gen that was intence btw srry for saying this but we just made our GUI
[Suggestion] VB Programmer Team
Originally Posted by Lolland
They should only hire people that can spell properly...
...oh wait, then there would be nobody in the team!
Anyways we've already had attempts at forming a VB coding team. They all failed because nobody here is committed enough to VB after they find out it takes effort to make hacks.
...oh wait, then there would be nobody in the team!
Anyways we've already had attempts at forming a VB coding team. They all failed because nobody here is committed enough to VB after they find out it takes effort to make hacks.
Ugh a lot of effort, but I don't have much else to do
And I'm not sure if CoD section allows hack teams...
Originally Posted by NextGen1
I have the dedication and patience.
Just, If I was going to be on a team, I would make it, and it would be constructed of a handful of people. (and I already know who they would be)
All would have a check in check out team version of VB.net (however they get their hands on it is their business
)
Each person would be assigned a task, no one is to touch the others task and so forth
Wanna know (IMO) why the teams here fail?
1. Alot of the "developers" in this section are students in school learning, they learned today how to make a message box, so they join and add 1337 in their sig and say their the best
------- Note: If you care about a team, you lay out what strengths you have , if any, if you are just learning to code and are joining a team, don't take on a difficult task, you may think making a layout , or a flowchart is "beneath you", but you should step up and just say "I can't do that"
2. Working together, when a team of people are randomly picked and used to write code, it ends in despair, randomness = carelessness. You now have 20 ppl who know how to make a spammer, but no one knows how to use Photoshop, or used API , so you never move forward.
-------Note: Programming together is similar to making a puzzle together, when you are all in the same room, all working on the same puzzle and all working on different parts, everything comes together nicely, but take that same puzzle, Give you all the same pieces and separate you all , when it's time to come together...nothing fits...
So if I was starting A VB team, It would Be
NextGen1 [Commercial Design,API]
Lolland / Bombsaway [Coders]
PixieCorp[Pixie] [outisde the box Ideas and concepts]
Why06 & Hell Demon[consultant]
Ali G [Graphics]
And that is it, (If i didn't say you, it doesn't mean I think you can't code , I have a good reason for my decision in the matter, Trust, Understanding, Knowing)
That's just offered as a (IMO) thing
Just, If I was going to be on a team, I would make it, and it would be constructed of a handful of people. (and I already know who they would be)
All would have a check in check out team version of VB.net (however they get their hands on it is their business
)Each person would be assigned a task, no one is to touch the others task and so forth
Wanna know (IMO) why the teams here fail?
1. Alot of the "developers" in this section are students in school learning, they learned today how to make a message box, so they join and add 1337 in their sig and say their the best
------- Note: If you care about a team, you lay out what strengths you have , if any, if you are just learning to code and are joining a team, don't take on a difficult task, you may think making a layout , or a flowchart is "beneath you", but you should step up and just say "I can't do that"
2. Working together, when a team of people are randomly picked and used to write code, it ends in despair, randomness = carelessness. You now have 20 ppl who know how to make a spammer, but no one knows how to use Photoshop, or used API , so you never move forward.
-------Note: Programming together is similar to making a puzzle together, when you are all in the same room, all working on the same puzzle and all working on different parts, everything comes together nicely, but take that same puzzle, Give you all the same pieces and separate you all , when it's time to come together...nothing fits...
So if I was starting A VB team, It would Be
NextGen1 [Commercial Design,API]
Lolland / Bombsaway [Coders]
PixieCorp[Pixie] [outisde the box Ideas and concepts]
Why06 & Hell Demon[consultant]
Ali G [Graphics]
And that is it, (If i didn't say you, it doesn't mean I think you can't code , I have a good reason for my decision in the matter, Trust, Understanding, Knowing)
That's just offered as a (IMO) thing
Ali G is from the GFX side of the forum.
Pixie is fine, He may not be great at VB, but neither is Why06 / Hell Demon / Ali G
They wouldn't be on for VB Coding
Pixie would be on for his ideas, ALI G for GFX , HEll Demon and Why06 for consulting / EX: how to do something I can't figure out in VB (for some reason) I can deduce from studying the C++ / C# concept.
(Just like my company)
Design Teams should consist of
* In Charge (1 person)
* Think Tank - 1-3 ppl depending on team or project.
* Consultants on a project (1-2 ppl you can trust with day day control as well as support)
* Coders (1-3)
* GFX (1-3, Depending on project)
* database designer (if needed)
If you just invite everyone into a team, it's going to fail,and so is the softeware, I know this from experience, I work commercially with people all day long , right now I am having problems with my Online OS for a client, because everyone comes together nicley, but the database guy is working on the GUI which he shouldn't be, so now we have conflicting code, because ASP.net doesn't blend well
Pixie is fine, He may not be great at VB, but neither is Why06 / Hell Demon / Ali G
They wouldn't be on for VB Coding
Pixie would be on for his ideas, ALI G for GFX , HEll Demon and Why06 for consulting / EX: how to do something I can't figure out in VB (for some reason) I can deduce from studying the C++ / C# concept.
(Just like my company)
Design Teams should consist of
* In Charge (1 person)
* Think Tank - 1-3 ppl depending on team or project.
* Consultants on a project (1-2 ppl you can trust with day day control as well as support)
* Coders (1-3)
* GFX (1-3, Depending on project)
* database designer (if needed)
If you just invite everyone into a team, it's going to fail,and so is the softeware, I know this from experience, I work commercially with people all day long , right now I am having problems with my Online OS for a client, because everyone comes together nicley, but the database guy is working on the GUI which he shouldn't be, so now we have conflicting code, because ASP.net doesn't blend well
I will join if you want... I'm good on VB ! Ready to make progs... !
Originally Posted by Wojek
I will join if you want... I'm good on VB ! Ready to make progs... !
XD
Lol i agree. We need proof. Our current members all have some specific area of skill, some people just can't see that.
This thread is closed for replies.
Similar Threads
Suggestions, Requests & General Help[Suggestion] Graphics Team
2 CrossFire Discussionssuggestions for hack programmersAB 7 Suggestions, Requests & General Help[Suggestion] Warez team
15 Suggestions, Requests & General Help[SuGgEStioN]no more wolf team!
2 WarRock - International HacksAny good game suggestions?
1
2 CrossFire Discussionssuggestions for hack programmersAB 7 Suggestions, Requests & General Help[Suggestion] Warez team 15 Suggestions, Requests & General Help[SuGgEStioN]no more wolf team! 2 WarRock - International HacksAny good game suggestions? 1